Triple
T30756195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Incomplete Enchanter |
E783090
|
entity |
| Predicate | containsWorld |
P180489
|
FINISHED |
| Object | Norse mythology world |
—
|
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: Norse mythology world | Statement: [The Incomplete Enchanter, containsWorld, Norse mythology world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsWorld Context triple: [The Incomplete Enchanter, containsWorld, Norse mythology world]
-
A.
hasWorld
Indicates that an entity possesses, is associated with, or encompasses a particular world or global context.
-
B.
hasPartOfWorld
chosen
Indicates that one entity includes or contains a specific region, section, or portion of the world as a component or subdivision of itself.
-
C.
isOnWorld
Indicates that one entity is located on, or exists upon the surface or within the domain of, a particular world or planet.
-
D.
hasWorldStructure
Indicates that an entity possesses or is characterized by a particular overall world-level organization, framework, or structural configuration.
-
E.
livesInWorldWith
Indicates that one entity exists or resides within the same world or universe as 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_69f224af8d8481908bea03890c5618be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff2fbae9b48190847eefa1c227d43e |
completed | May 9, 2026, 12:59 p.m. |
| PD | Predicate disambiguation | batch_69ff2f2218048190a32224a648182b5d |
completed | May 9, 2026, 12:57 p.m. |
Created at: April 29, 2026, 8:39 p.m.