Triple
T8130038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Moon of Gomrath |
E189829
|
entity |
| Predicate | hasMagicSystem |
P19914
|
FINISHED |
| Object | old 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: old magic | Statement: [The Moon of Gomrath, hasMagicSystem, old magic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMagicSystem Context triple: [The Moon of Gomrath, hasMagicSystem, old magic]
-
A.
hasMagicSystemElement
Indicates that an entity’s magic system includes or is characterized by a specific elemental component or aspect.
-
B.
hasLimitedMagic
Indicates that an entity possesses magical abilities that are restricted in scope, power, frequency, or conditions of use.
-
C.
usesMagic
Indicates that an entity performs actions or achieves effects by employing magical powers or supernatural abilities.
-
D.
usesMagicFor
Indicates that one entity employs or applies magic as a means to achieve, affect, or perform something involving another entity or context.
-
E.
typeOfMagic
chosen
Indicates that one entity is a specific category, school, or kind of magic associated with 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_69ca82bcb4848190a9a9d036ad768642 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4c4c2e388190b86854f8b1765e61 |
completed | March 31, 2026, 4:23 a.m. |
| PD | Predicate disambiguation | batch_69cb3696379c8190a20965e59ed8f370 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:34 p.m.