Triple
T4257237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telesterion at Eleusis |
E96004
|
entity |
| Predicate | finalDestruction |
P11808
|
FINISHED |
| Object | late 4th century CE |
—
|
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: late 4th century CE | Statement: [Telesterion at Eleusis, finalDestruction, late 4th century CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalDestruction Context triple: [Telesterion at Eleusis, finalDestruction, late 4th century CE]
-
A.
typeOfDestruction
Indicates the specific manner or method by which something is destroyed or caused to cease to exist.
-
B.
destroyedDuring
chosen
Indicates that one entity was destroyed in the course of, or as a consequence of, a specified event or time period.
-
C.
finalPhaseOf
Indicates that one process, stage, or event constitutes the concluding or last phase of another broader process or sequence.
-
D.
demolitionEnd
Indicates the point in time or event at which a demolition process is completed or comes to an end.
-
E.
purposeOfDestruction
Indicates that something is destroyed with the specific aim or intention of achieving a particular goal or outcome.
- 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_69b3454095ac81909c2494f7ff294af1 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34ec321008190b2cc1aca6ab690c4 |
completed | March 12, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69b347f73e008190a908a48ef389945a |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:06 p.m.