Triple
T29341674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infinity Engine |
E744051
|
entity |
| Predicate | gameRulesSystem |
P6601
|
FINISHED |
| Object | Dungeons & Dragons |
—
|
NE NERFINISHED |
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: Dungeons & Dragons | Statement: [Infinity Engine, gameRulesSystem, Dungeons & Dragons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameRulesSystem Context triple: [Infinity Engine, gameRulesSystem, Dungeons & Dragons]
-
A.
deathGameRule
Indicates a rule or condition within a deadly or lethal game that governs how participants must act or what consequences they face.
-
B.
affectedByGameRule
Indicates that an entity’s state, behavior, or outcome is influenced or constrained by a specific game rule.
-
C.
playedUnderRulesOf
chosen
Indicates that an activity or game was conducted in accordance with a specified set of rules or regulations.
-
D.
rulesSystem
Indicates that an entity establishes, governs, or defines the rules or structure by which another system or process operates.
-
E.
gameLengthRule
Indicates a rule that specifies how long a game is allowed or required to last.
- 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f66926e7a48190a1b580fd9fe67c31 |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:34 p.m.