Triple
T38583805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hellfire Peninsula |
E932300
|
entity |
| Predicate | notableNPCFaction |
P120153
|
FINISHED |
| Object | Cenarion Expedition |
E2241541
|
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: Cenarion Expedition | Statement: [Hellfire Peninsula, notableNPCFaction, Cenarion Expedition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableNPCFaction Context triple: [Hellfire Peninsula, notableNPCFaction, Cenarion Expedition]
-
A.
notableNobleFaction
Indicates that a noble is significantly associated with or belongs to a particularly prominent or influential noble faction.
-
B.
notableCharacterAffiliation
chosen
Indicates that a notable character is formally associated with, aligned to, or a member of a particular group, organization, or affiliation.
-
C.
factionVariantNPC
Indicates that an NPC is a variant or subtype associated with a particular faction within the game world.
-
D.
controlledByFaction
Indicates that an entity is under the authority, influence, or governance of a particular faction.
-
E.
portraysFaction
Indicates that one entity depicts, represents, or characterizes a particular faction or group, typically in a narrative, artistic, or media context.
- 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_6a41f43924cc8190b03f5c8d442f4e7f |
completed | June 29, 2026, 4:27 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.