Triple
T29341703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aurora Engine |
E744052
|
entity |
| Predicate | rulesSupport |
P104471
|
FINISHED |
| Object | Dungeons & Dragons 3rd Edition-derived rules |
—
|
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: Dungeons & Dragons 3rd Edition-derived rules | Statement: [Aurora Engine, rulesSupport, Dungeons & Dragons 3rd Edition-derived rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rulesSupport Context triple: [Aurora Engine, rulesSupport, Dungeons & Dragons 3rd Edition-derived rules]
-
A.
supportRules
Indicates that one entity provides justification, backing, or validation for the rules or constraints defined by another entity.
-
B.
theorySupports
Indicates that one theory provides justification, evidence, or logical backing for another claim, theory, or proposition.
-
C.
supportsRuleType
chosen
Indicates that one entity is capable of handling, applying, or being compatible with a specified type of rule.
-
D.
alsoSupports
Indicates that an entity, in addition to its primary or previously stated function, provides support for another entity, feature, or activity.
-
E.
rulesBy
Indicates that one entity governs, controls, or exercises authoritative power over another entity.
- 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.