Triple
T37763428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zangarmarsh |
E941345
|
entity |
| Predicate | primaryControllingFactionNPC |
P194662
|
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: [Zangarmarsh, primaryControllingFactionNPC, Cenarion Expedition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryControllingFactionNPC Context triple: [Zangarmarsh, primaryControllingFactionNPC, Cenarion Expedition]
-
A.
ownerFactionCapital
Indicates that a faction serves as the owning or controlling capital of a given entity.
-
B.
factionVariantNPC
Indicates that an NPC is a variant or subtype associated with a particular faction within the game world.
-
C.
controlledByFaction
chosen
Indicates that an entity is under the authority, influence, or governance of a particular faction.
-
D.
protagonistAllegiance
Indicates the group, cause, or side with which the main character is aligned or to which they show loyalty.
-
E.
finalBossFaction
Indicates that an entity serves as or belongs to the faction of the ultimate or final boss in a game or narrative.
- 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_69f76ee3251881909bb4451aad50752b |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40f178dea4819092ef0f7be9da3f30 |
completed | June 28, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:19 p.m.