Triple
T12797966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Tragedy of Great Power Politics |
E305936
|
entity |
| Predicate | setsForthTheoryOf |
P38287
|
FINISHED |
| Object | great power behavior |
—
|
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: great power behavior | Statement: [The Tragedy of Great Power Politics, setsForthTheoryOf, great power behavior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setsForthTheoryOf Context triple: [The Tragedy of Great Power Politics, setsForthTheoryOf, great power behavior]
-
A.
hasTheory
Indicates that an entity possesses, is associated with, or is characterized by a particular theory.
-
B.
followsTheoryOf
Indicates that one entity adheres to, is based on, or is guided by the theoretical framework or principles established by another entity.
-
C.
developsTheory
Indicates that one entity formulates, elaborates, or advances a theoretical framework or explanation concerning another entity.
-
D.
theorized
Indicates that one entity has proposed or developed a theoretical explanation or hypothesis about another entity or phenomenon.
-
E.
presentsTheory
chosen
Indicates that one entity formally puts forward or explains a theory to another entity or audience.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e6f858c8190915ede38e9a6a2df |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ed7448190b276e7fab649f7d2 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:30 p.m.