Triple
T14450059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2020 Civil War game |
E358305
|
entity |
| Predicate | rivalryRenamingContext |
P30638
|
FINISHED |
| Object | use of name "Civil War" later discontinued by schools |
—
|
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: use of name "Civil War" later discontinued by schools | Statement: [2020 Civil War game, rivalryRenamingContext, use of name "Civil War" later discontinued by schools]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rivalryRenamingContext Context triple: [2020 Civil War game, rivalryRenamingContext, use of name "Civil War" later discontinued by schools]
-
A.
rivalryName
Indicates that a specific name or label is assigned to a rivalry relationship between two entities.
-
B.
contextOfRenaming
chosen
Indicates the situational or historical context in which an entity’s name was or is being changed.
-
C.
rivalryNameStyle
Indicates a stylistic or conventional way in which the name of a rivalry between entities is expressed or formatted.
-
D.
rivalryBasis
Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
-
E.
hasRivalryContext
Indicates that there exists a competitive or adversarial relationship between entities within a specific situational or contextual framework.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de916139888190be219678e29a2a3a |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:19 a.m.