Triple
T3965349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anthesteria |
E92203
|
entity |
| Predicate | timeInAtticCalendar |
P53648
|
FINISHED |
| Object | month of Anthesterion |
—
|
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: month of Anthesterion | Statement: [Anthesteria, timeInAtticCalendar, month of Anthesterion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInAtticCalendar Context triple: [Anthesteria, timeInAtticCalendar, month of Anthesterion]
-
A.
timeExistence
Indicates the period or duration during which an entity exists or is valid.
-
B.
chronologicalFunction
Indicates a temporal relationship where one event or state functions to order, structure, or position another within a sequence of time.
-
C.
calendarEpoch
Indicates the reference starting point in time from which a particular calendar system counts its dates.
-
D.
dateApproximate
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
E.
yearCirca
Indicates that the associated year is approximate or uncertain rather than exact.
- 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_69aed96624188190ac8c45bb57ab72b5 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefba878a48190a2e234d775215938 |
completed | March 9, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69aef8efcf3c81908ccf61d9ce26b0c0 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefba6b9848190a7b0fb66100a2a0c |
completed | March 9, 2026, 4:56 p.m. |
Created at: March 9, 2026, 3:31 p.m.