Triple
T12797961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Tragedy of Great Power Politics |
E305936
|
entity |
| Predicate | widelyUsedAs |
P2506
|
FINISHED |
| Object | university textbook |
—
|
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: university textbook | Statement: [The Tragedy of Great Power Politics, widelyUsedAs, university textbook]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: widelyUsedAs Context triple: [The Tragedy of Great Power Politics, widelyUsedAs, university textbook]
-
A.
widelyUsedIn
Indicates that something is commonly or extensively utilized within a particular context, domain, or group.
-
B.
isFamouslyUsedIn
Indicates that something is widely recognized or well-known for being used in a particular context, work, or situation.
-
C.
isFamouslyUsedBy
Indicates that something is widely and notably used by a particular person, group, or entity, in a way that is broadly recognized or associated with them.
-
D.
isUsedAs
chosen
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
E.
isAlsoUsedAs
Indicates that something serves an additional function or role beyond its primary one.
- 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.