Triple
T23744722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clash of Civilizations |
E586781
|
entity |
| Predicate | usedToInterpret |
P3638
|
FINISHED |
| Object | post–Cold War conflicts |
—
|
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: post–Cold War conflicts | Statement: [Clash of Civilizations, usedToInterpret, post–Cold War conflicts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedToInterpret Context triple: [Clash of Civilizations, usedToInterpret, post–Cold War conflicts]
-
A.
areInterpretedInPracticeBy
Indicates that something (such as a rule, concept, or specification) is given concrete meaning or applied in real-world situations by a particular agent or group.
-
B.
usedToExplain
chosen
Indicates that one entity serves as an explanation or clarification for another entity.
-
C.
frequentlyInterpretedBy
Indicates that an entity is often or regularly interpreted, explained, or given meaning by a particular agent or group.
-
D.
intendedInterpretation
Indicates that one entity is meant to be understood or interpreted in a particular way, sense, or meaning relative to another.
-
E.
containsInterpretationOf
Indicates that one entity includes or embodies an interpretation or understanding 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_69e24908efb08190bf755c3a9b91f222 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bcbcc4f88190a00fceeafbfb5cfd |
completed | April 29, 2026, 8:09 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:12 p.m.