Triple
T18449870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexiares |
E450750
|
entity |
| Predicate | hasDivineLineage |
P61606
|
FINISHED |
| Object | son of Heracles |
—
|
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 Heracles | Statement: [Alexiares, hasDivineLineage, son of Heracles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDivineLineage Context triple: [Alexiares, hasDivineLineage, son of Heracles]
-
A.
hasPriestlyLineage
Indicates that an entity descends from, or belongs to, a recognized priestly family or hereditary priestly line.
-
B.
divineLineage
chosen
Indicates that one entity is descended from, or originates from, a divine or god-like being.
-
C.
hasMortalOrSemiDivineAncestry
Indicates that an entity descends from, or is otherwise ancestrally connected to, beings who are mortal or possess semi-divine (partly divine) status.
-
D.
hasParentDeity
Indicates that one deity is the parent (progenitor or creator) of another deity.
-
E.
hasViewOnDivinity
Indicates that an entity holds a particular belief, opinion, or perspective regarding divinity or the nature of the divine.
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5264748dc8190984501af3e4b2036 |
completed | April 19, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e469d05cf4819099baf1665a9cf18a |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:30 a.m.