Triple
T38587514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First War |
E932377
|
entity |
| Predicate | primaryHumanKingdomInvolved |
P206554
|
FINISHED |
| Object | Stormwind |
E932363
|
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: Stormwind | Statement: [First War, primaryHumanKingdomInvolved, Stormwind]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryHumanKingdomInvolved Context triple: [First War, primaryHumanKingdomInvolved, Stormwind]
-
A.
hasBiologicalKingdom
Indicates that a biological organism is classified as belonging to a particular kingdom in the taxonomic hierarchy.
-
B.
hasSubkingdom
Indicates that one biological kingdom is divided into, or associated with, a specific subkingdom as a subordinate taxonomic rank.
-
C.
kingdomDomain
Indicates that a kingdom is part of, or belongs within, a particular higher-level domain.
-
D.
organismDomain
Indicates the taxonomic domain to which an organism belongs.
-
E.
targetOrganism
Indicates that an action, process, or effect is directed toward or intended to impact a particular organism.
- 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_6a420dfd78488190a629a809d5904c2b |
completed | June 29, 2026, 6:17 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.