Triple
T35830656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sargeras |
E1035787
|
entity |
| Predicate | realmOfInfluence |
P2828
|
FINISHED |
| Object | cosmic-scale Warcraft cosmology |
—
|
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: cosmic-scale Warcraft cosmology | Statement: [Sargeras, realmOfInfluence, cosmic-scale Warcraft cosmology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: realmOfInfluence Context triple: [Sargeras, realmOfInfluence, cosmic-scale Warcraft cosmology]
-
A.
realmRuled
Indicates that one entity serves as the sovereign or governing ruler over a particular realm, territory, or domain.
-
B.
mainTerritoryOfInfluence
Indicates the primary geographic area where an entity exerts the most significant control, impact, or influence.
-
C.
sphereOfInfluence
chosen
Indicates the area or domain within which an entity exerts significant control, impact, or authority over others.
-
D.
realmWithin
Indicates that one realm or domain is contained inside, or exists as a subset of, another realm or domain.
-
E.
realmCenter
Indicates that one entity serves as the central or focal point of a given realm, domain, or spatial region in relation to 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_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.