Triple
T29655217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nexus |
E750244
|
entity |
| Predicate | lossCondition |
P43002
|
FINISHED |
| Object | destruction can lead to defeat if no other Nexuses remain |
—
|
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: destruction can lead to defeat if no other Nexuses remain | Statement: [Nexus, lossCondition, destruction can lead to defeat if no other Nexuses remain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lossCondition Context triple: [Nexus, lossCondition, destruction can lead to defeat if no other Nexuses remain]
-
A.
loserStatus
Indicates that an entity has been judged or designated as the loser in a particular comparison, contest, or evaluative context.
-
B.
losingState
Indicates that a particular game or competitive situation is in a condition where the player or side in question is currently losing or destined to lose under optimal play.
-
C.
loserScore
Indicates the number of points or score achieved by the losing participant in a competitive event or comparison.
-
D.
loserPoints
Indicates the number of points awarded to or accumulated by the losing side in a competitive event or comparison.
-
E.
lossType
chosen
Indicates the specific category or nature of a loss associated with an entity or event.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f66f274ba08190bcdbdfeccf4af09d |
completed | May 2, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:54 p.m.