Triple
T36959451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Total Annihilation |
E914269
|
entity |
| Predicate | followsConflictBetween |
P199736
|
FINISHED |
| Object | Arm |
—
|
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: Arm | Statement: [Total Annihilation, followsConflictBetween, Arm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsConflictBetween Context triple: [Total Annihilation, followsConflictBetween, Arm]
-
A.
conflictWith
Indicates that two entities are in opposition or disagreement, such that their goals, actions, or states are incompatible or interfere with each other.
-
B.
subsequentConflict
Indicates that one conflict occurs after and is temporally subsequent to another conflict.
-
C.
followsConflictPhase
Indicates that one conflict phase occurs after and is temporally subsequent to another conflict phase.
-
D.
conflictedBetween
Indicates being torn or uncertain between two or more options, positions, or commitments.
-
E.
linkedConflict
Indicates a relationship where one conflict is directly associated with, related to, or dependent on another conflict.
- F. None of above. chosen
Provenance (4 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff5285ed74819097e6e2a9084a079a |
completed | May 9, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69ff51fbe28881908ac8417dff9db81a |
completed | May 9, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69ff528536d481909caefe52fcd8aaa7 |
completed | May 9, 2026, 3:28 p.m. |
Created at: May 3, 2026, 4:13 p.m.