Triple
T36254456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phoebe |
E891894
|
entity |
| Predicate | successorAsDelphicOracle |
P202191
|
FINISHED |
| Object | Apollo |
—
|
NE NERFINISHED |
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: Apollo | Statement: [Phoebe, successorAsDelphicOracle, Apollo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAsDelphicOracle Context triple: [Phoebe, successorAsDelphicOracle, Apollo]
-
A.
prophecyHeldBy
Indicates that a particular prophecy is possessed, guarded, or maintained by a specific holder.
-
B.
prophecyHeardBy
Indicates that a prophecy was heard or received by a particular entity.
-
C.
prophecyKnownAs
Indicates that a particular prophecy is referred to or recognized by a specific name or title.
-
D.
successorAsHighPriestOfAmun
Indicates that one individual directly followed another in holding the position of High Priest of Amun.
-
E.
predecessorInMyth
Indicates that one mythological figure, story, or element chronologically or narratively comes before and influences or sets the stage for another within a mythic tradition.
- F. None of above. chosen
Provenance (4 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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a005e8a2f7c819085bfc6f04b866d87 |
completed | May 10, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_6a005de82ef08190a015b385d1d3443c |
completed | May 10, 2026, 10:28 a.m. |
| PDg | Predicate description generation | batch_6a005e89803c8190ad732ad15affb81f |
completed | May 10, 2026, 10:31 a.m. |
Created at: May 3, 2026, 4:09 p.m.