Triple
T19256164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amphion |
E481521
|
entity |
| Predicate | divineParentage |
P20192
|
FINISHED |
| Object | son of Zeus |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: son of Zeus | Statement: [Amphion, divineParentage, son of Zeus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divineParentage Context triple: [Amphion, divineParentage, son of Zeus]
-
A.
divineLineage
Indicates that one entity is descended from, or originates from, a divine or god-like being.
-
B.
divineFather
chosen
Indicates a paternal relationship in which one entity is regarded as the godly or divine father of another.
-
C.
hasParentDeity
Indicates that one deity is the parent (progenitor or creator) of another deity.
-
D.
spiritualSonOf
Indicates a relationship where one person is regarded as the spiritual or religious protégé, disciple, or mentee of another, akin to a parent–child bond in a non-biological, faith-based context.
-
E.
incarnationOf
Indicates that one entity is a concrete embodiment, manifestation, or earthly form of another, typically more abstract or divine, entity.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb3572c08190a55f1c71cdb18b42 |
completed | April 20, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:28 p.m.