Triple
T35830254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second War |
E1035778
|
entity |
| Predicate | setOnWorld |
P141016
|
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: [Second War, setOnWorld, Azeroth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setOnWorld Context triple: [Second War, setOnWorld, Azeroth]
-
A.
isOnWorld
chosen
Indicates that one entity is located on, or exists upon the surface or within the domain of, a particular world or planet.
-
B.
hasViewOnWorld
Indicates that an entity holds a particular perspective, opinion, or interpretation regarding the world or reality as a whole.
-
C.
setInUniverse
Indicates that something is located within, belongs to, or takes place in a particular fictional or conceptual universe.
-
D.
effectOnWorld
Indicates how an entity’s actions or existence change, influence, or impact the state of the world.
-
E.
setsOn
Indicates that one entity places or arranges another entity onto a specified surface, container, or context.
- 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_69f76e192a94819082db360cb91e6a8d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.