Triple
T1386374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollodorus of Athens |
E29854
|
entity |
| Predicate | Chronica_endingPoint |
P25377
|
FINISHED |
| Object | mid-2nd century BCE |
—
|
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: mid-2nd century BCE | Statement: [Apollodorus of Athens, Chronica_endingPoint, mid-2nd century BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Chronica_endingPoint Context triple: [Apollodorus of Athens, Chronica_endingPoint, mid-2nd century BCE]
-
A.
isFinalChapterOf
Indicates that one entity is the concluding or last chapter within the sequence of chapters of another entity (typically a work or volume).
-
B.
eraEnd
chosen
Indicates the point in time or event at which a particular era, period, or phase comes to a close.
-
C.
hasTragicEnding
Indicates that the event, story, or situation concludes with a sorrowful, disastrous, or otherwise deeply unfortunate outcome.
-
D.
narrativeEnd
Indicates the point or event at which a narrative, story, or discourse concludes or is brought to an end.
-
E.
endOfReign
Indicates the point in time or event at which a ruler’s or leader’s period of authority or reign concludes.
- 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_69a498dc92f8819094a1108f8ac90f43 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c339f3d481909c04b14129899945 |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4beffcf808190ab4cd0271257ce63 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.