Triple
T36886880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kroton |
E911634
|
entity |
| Predicate | foundationLegend |
P199302
|
FINISHED |
| Object | oracle of Delphi |
—
|
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: oracle of Delphi | Statement: [Kroton, foundationLegend, oracle of Delphi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundationLegend Context triple: [Kroton, foundationLegend, oracle of Delphi]
-
A.
featuredLegend
Indicates that an entity is highlighted or showcased as a prominent or notable legend within a given context.
-
B.
regionOfLegend
Indicates the geographic area or locale with which a particular legend or myth is associated.
-
C.
mentionsLegend
Indicates that one entity makes reference to or cites a legendary figure, story, or concept associated with another entity.
-
D.
foundationEvent
Indicates the event or act through which something (such as an organization, institution, or structure) is formally established or created.
-
E.
basedInLegend
Indicates that something is located, rooted, or primarily known within the context of a legend or mythic narrative.
- 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_69f76e8335908190b77e7e11d0e80820 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff2d22ffb48190ae58ddf3c7e02869 |
completed | May 9, 2026, 12:48 p.m. |
| PD | Predicate disambiguation | batch_69ff2ac2e1c4819096cc64e94aef2ff0 |
completed | May 9, 2026, 12:38 p.m. |
| PDg | Predicate description generation | batch_69ff2d21f0a48190ad2ef5901cb07d93 |
completed | May 9, 2026, 12:48 p.m. |
Created at: May 3, 2026, 4:13 p.m.