Triple
T36254455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phoebe |
E891894
|
entity |
| Predicate | predecessorAsDelphicOracle |
P50182
|
FINISHED |
| Object | Themis |
—
|
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: Themis | Statement: [Phoebe, predecessorAsDelphicOracle, Themis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorAsDelphicOracle Context triple: [Phoebe, predecessorAsDelphicOracle, Themis]
-
A.
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.
-
B.
predecessorDeityOfSite
chosen
Indicates that a deity previously associated with or worshipped at a site served as an earlier or former divine figure relative to another deity linked to that same site.
-
C.
predecessor
Indicates that one entity comes before another in an ordered sequence or succession.
-
D.
predecessorName
Indicates that the value is the name of an entity that directly precedes another in an ordered sequence or lineage.
-
E.
predecessorAvatar
Indicates that one avatar existed or was used before another avatar in a temporal or version sequence.
- 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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
Created at: May 3, 2026, 4:09 p.m.