Triple
T8953741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaneš |
E213419
|
entity |
| Predicate | destroyedMultipleTimes |
P85850
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Kaneš, destroyedMultipleTimes, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: destroyedMultipleTimes Context triple: [Kaneš, destroyedMultipleTimes, true]
-
A.
rebuiltMultipleTimes
Indicates that the same entity has been reconstructed or restored on more than one separate occasion.
-
B.
destroyedDuring
Indicates that one entity was destroyed in the course of, or as a consequence of, a specified event or time period.
-
C.
hasMultipleCreations
Indicates that an entity is associated with more than one distinct creation or produced work.
-
D.
wasDestroyedOrTransformed
Indicates that an entity ceased to exist in its original form due to being either destroyed or fundamentally transformed.
-
E.
typeOfDestruction
Indicates the specific manner or method by which something is destroyed or caused to cease to exist.
- 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_69ca8399ad2081909f8fa41d4314c215 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc670f88d0819085d7308a5cf6c764 |
completed | April 1, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed74d288190b712d739805579dc |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f887108819096d45a186fc137b3 |
completed | March 31, 2026, 11:58 p.m. |
Created at: March 30, 2026, 7 p.m.