Triple
T26126926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Land of Spells |
E659129
|
entity |
| Predicate | lawsOfNature |
P131424
|
FINISHED |
| Object | governed by magic |
—
|
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: governed by magic | Statement: [The Land of Spells, lawsOfNature, governed by magic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lawsOfNature Context triple: [The Land of Spells, lawsOfNature, governed by magic]
-
A.
natureOfRule
Indicates the fundamental type or character of a rule, specifying what kind of rule it is or how it functions within a system.
-
B.
natureOfForces
Indicates the fundamental type or character of the forces involved in an interaction or system.
-
C.
natureIsClearlyDefined
Indicates that the inherent characteristics, boundaries, or essential qualities of something are explicitly and unambiguously specified.
-
D.
governingForceOf
chosen
Indicates that one entity functions as the primary controlling or directing influence over another entity’s behavior, state, or dynamics.
-
E.
authorityNature
Indicates the type or character of authority one entity holds or exercises over another.
- 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_69ee5bc2b2948190b458ad3f580af779 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60b8fc5748190803051bc9c8c46cb |
completed | May 2, 2026, 2:34 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:12 p.m.