Triple
T20349174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dragon Challenge |
E495962
|
entity |
| Predicate | reasonForDuelingDisabled |
P139785
|
FINISHED |
| Object | safety concerns |
—
|
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: safety concerns | Statement: [Dragon Challenge, reasonForDuelingDisabled, safety concerns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForDuelingDisabled Context triple: [Dragon Challenge, reasonForDuelingDisabled, safety concerns]
-
A.
legalStatusOfDuel
Indicates the legal status or permissibility of engaging in a duel within a given jurisdiction or context.
-
B.
typeOfDuel
Indicates the specific kind or category of duel that characterizes a given dueling event or relationship between opponents.
-
C.
reasonForDisqualification
Indicates the specific cause or justification for which an entity was deemed ineligible or disqualified from consideration or participation.
-
D.
duelArrangedBy
Indicates that a duel between two parties has been set up, initiated, or formally organized by a specific agent or entity.
-
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. 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_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. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:24 a.m.