Triple
T38587477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SI:7 |
E932376
|
entity |
| Predicate | operatesOnWorld |
P206552
|
FINISHED |
| Object | Azeroth |
E273692
|
NE 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: Azeroth | Statement: [SI:7, operatesOnWorld, Azeroth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesOnWorld Context triple: [SI:7, operatesOnWorld, Azeroth]
-
A.
isOnWorld
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.
effectOnWorld
Indicates how an entity’s actions or existence change, influence, or impact the state of the world.
-
D.
hasWorld
Indicates that an entity possesses, is associated with, or encompasses a particular world or global context.
-
E.
operatesOnPhysicalSystem
Indicates that an agent or process performs actions that affect or manipulate a physical system.
- F. None of above. chosen
Provenance (5 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4312f43c6c819084aad3e93f1b9409 |
completed | June 30, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c85e308819083dd67b96f457659 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:32 p.m.