Triple
T14749205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Life of Theseus |
E346558
|
entity |
| Predicate | setInNarrativeTime |
P11197
|
FINISHED |
| Object | mythic past of Athens |
—
|
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: mythic past of Athens | Statement: [Life of Theseus, setInNarrativeTime, mythic past of Athens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setInNarrativeTime Context triple: [Life of Theseus, setInNarrativeTime, mythic past of Athens]
-
A.
timeOfNarrative
chosen
Indicates the specific time or period during which the events of a narrative are set or unfold.
-
B.
setInFictionalYear
Indicates that the events or narrative of a work are situated in a specified fictional or non-real calendar year.
-
C.
narrativeMoment
Indicates the specific point or phase within a narrative at which an event, action, or relationship occurs.
-
D.
hasNarrativeEvent
Indicates that one entity includes, contains, or is associated with a specific narrative event within a story or sequence of events.
-
E.
hasPartInNarrative
Indicates that one entity plays a role or participates as a component within the storyline or structure of another narrative entity.
- 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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7d2e1748190b16ede681fe52872 |
completed | April 14, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69de8bf9331481909582045cd567d91f |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:30 a.m.