Triple
T6073864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tauresium |
E135349
|
entity |
| Predicate | timeOfDestruction |
P68493
|
FINISHED |
| Object | 6th century |
—
|
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: 6th century | Statement: [Tauresium, timeOfDestruction, 6th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfDestruction Context triple: [Tauresium, timeOfDestruction, 6th century]
-
A.
typeOfDestruction
Indicates the specific manner or method by which something is destroyed or caused to cease to exist.
-
B.
yearOfDestruction
Indicates the specific year in which an entity was destroyed or ceased to exist.
-
C.
locationOfDestruction
Indicates the place where a destruction event occurred or where something was destroyed.
-
D.
designedToDestroy
Indicates that one entity was intentionally created or configured for the purpose of damaging, disabling, or annihilating another entity.
-
E.
hasCauseOfDestruction
Indicates that one entity is the cause or agent responsible for the destruction or damage of another entity.
- 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_69c00879e8048190b690717d19c5bc03 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0575b9bc08190a78b3082b9ccf00c |
completed | March 22, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69c049f21fe08190995df3c5c05fb8ea |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8d4a148190bd8f95caae978e1b |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:11 p.m.