Triple
T12932984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gordium archaeological site |
E309427
|
entity |
| Predicate | timeOfMajorDestruction |
P48488
|
FINISHED |
| Object | late 8th 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: late 8th century BCE | Statement: [Gordium archaeological site, timeOfMajorDestruction, late 8th century BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfMajorDestruction Context triple: [Gordium archaeological site, timeOfMajorDestruction, late 8th century BCE]
-
A.
timePeriodOfMajorDestruction
chosen
Indicates the time span during which a major destructive event affecting the subject occurred.
-
B.
timeOfDestruction
Indicates the specific time at which an entity is destroyed or ceases to exist.
-
C.
sufferedDestructionIn
Indicates that an entity experienced damage, ruin, or devastation during or as part of a specified event or period.
-
D.
yearOfDestruction
Indicates the specific year in which an entity was destroyed or ceased to exist.
-
E.
hasCauseOfDestruction
Indicates that one entity is the cause or agent responsible for the destruction or damage of another 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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97db69f548190a1a693bc0d6c191a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 5:42 p.m.