Triple
T5407007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Othrys |
E120916
|
entity |
| Predicate | locatedInNarrativeWorld |
P59480
|
FINISHED |
| Object | cosmology of Greek mythology |
—
|
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: cosmology of Greek mythology | Statement: [Mount Othrys, locatedInNarrativeWorld, cosmology of Greek mythology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInNarrativeWorld Context triple: [Mount Othrys, locatedInNarrativeWorld, cosmology of Greek mythology]
-
A.
setInFictionalLocation
Indicates that an event, story, or narrative takes place within a fictional or imagined location rather than a real-world setting.
-
B.
narrativeLocationType
Indicates the type or role of a location within the structure or context of a narrative (e.g., setting, origin, destination).
-
C.
storyWorld
chosen
Indicates the fictional universe or narrative setting within which a story, event, or character exists or takes place.
-
D.
locationOfNarrative
Indicates the place or setting where the events or story described in the narrative occur.
-
E.
locatedInFictionalCountry
Indicates that an entity exists or is situated within a country that is fictional rather than real.
- 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_69bd46391c0c81909fa484446732b6a3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8793ab3c81909992b257d462a554 |
completed | March 20, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69bd8467e6b48190b9eaa9de67072e06 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:05 p.m.