Triple
T38584315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyjal Summit |
E932311
|
entity |
| Predicate | featuresNPCAlly |
P188232
|
FINISHED |
| Object | Jaina Proudmoore |
E273696
|
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: Jaina Proudmoore | Statement: [Hyjal Summit, featuresNPCAlly, Jaina Proudmoore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresNPCAlly Context triple: [Hyjal Summit, featuresNPCAlly, Jaina Proudmoore]
-
A.
protagonistAlly
Indicates that one entity serves as an ally, supporter, or close associate of the story’s main protagonist.
-
B.
factionVariantNPC
Indicates that an NPC is a variant or subtype associated with a particular faction within the game world.
-
C.
primaryAlly
Indicates that one entity is the main or most significant ally or supportive partner of another entity.
-
D.
isPlayableAllyOf
chosen
Indicates that one entity can be used or controlled as an ally in conjunction with another entity, typically within a game or interactive context.
-
E.
featuresFictionalUnit
Indicates that something includes or presents a fictional unit (such as a character, group, or organization) as part of its content or structure.
- F. None of above.
Provenance (4 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_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4205b2062481908dfa7165c2049e65 |
completed | June 29, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.