Triple
T37553389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valley of Spirits zeppelin tower |
E933639
|
entity |
| Predicate | foundInWorld |
P9687
|
FINISHED |
| Object | Azeroth |
—
|
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: Azeroth | Statement: [Valley of Spirits zeppelin tower, foundInWorld, Azeroth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundInWorld Context triple: [Valley of Spirits zeppelin tower, foundInWorld, Azeroth]
-
A.
foundInRegion
chosen
Indicates that something is located within, occurs in, or is associated with a specific geographic or spatial region.
-
B.
discoveredForWorld
Indicates that something was discovered or revealed specifically for the benefit, use, or knowledge of the world at large.
-
C.
wasDiscoveredIn
Indicates that an entity became known or was first identified during a specific time period or at a particular place.
-
D.
foundInRite
Indicates that something (such as an element, object, or action) occurs within, is used in, or is otherwise present as part of a specific rite or ritual.
-
E.
inhabitedIn
Indicates that an entity lives, resides, or has its dwelling within a specified place or location.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff45793d5c81909dc503ad1f714ee2 |
completed | May 9, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69ff41cb0e088190a6e9b03cb20e5fad |
completed | May 9, 2026, 2:16 p.m. |
Created at: May 3, 2026, 4:17 p.m.