Triple
T18711001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kirrha |
E457511
|
entity |
| Predicate | outcomeOfWar |
P12962
|
FINISHED |
| Object | destruction of the city |
—
|
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: destruction of the city | Statement: [Kirrha, outcomeOfWar, destruction of the city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outcomeOfWar Context triple: [Kirrha, outcomeOfWar, destruction of the city]
-
A.
concludedWar
Indicates that a war or armed conflict between entities has come to an end, typically through victory, surrender, or formal agreement.
-
B.
postwarOutcome
chosen
Indicates the result or consequences that follow for a party or situation after a war has ended.
-
C.
warEndedHere
Indicates that a particular war or armed conflict came to its conclusion at this location.
-
D.
legalStatusAfterWar
Indicates the legal condition or classification assigned to an entity as a consequence of, or following the conclusion of, a war or armed conflict.
-
E.
hasPrimaryBelligerentDefeated
Indicates that the primary belligerent in a conflict or confrontation has been defeated by another party.
- 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_69d8d392aad081909fe31aa03e6e97d1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5671b34508190b6180f7d6ad50a58 |
completed | April 19, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69e478e0889c8190a118d67b200ce8ef |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:50 a.m.