Triple
T20349173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dragon Challenge |
E495962
|
entity |
| Predicate | duelingFeatureDisabled |
P11582
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Dragon Challenge, duelingFeatureDisabled, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: duelingFeatureDisabled Context triple: [Dragon Challenge, duelingFeatureDisabled, 2011]
-
A.
typeOfDuel
Indicates the specific kind or category of duel that characterizes a given dueling event or relationship between opponents.
-
B.
disabledByDefaultIn
chosen
Indicates that a feature, capability, or setting is turned off by default within the specified context or environment.
-
C.
rivalryFeature
Indicates a competitive or adversarial relationship between entities, often characterized by ongoing opposition or comparison.
-
D.
rudderDisabledBy
Indicates that a rudder becomes nonfunctional or inoperative as a result of the specified cause or agent.
-
E.
isClimacticDuelOf
Indicates that one event or confrontation serves as the decisive, peak showdown within the narrative arc of another event or storyline.
- 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_69e0b4a3320881909495ae8bc30bc2dc |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6783af5dc8190a40c3b9816cd1aef |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:24 a.m.