Triple
T37872871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Shado-Pan |
E944647
|
entity |
| Predicate | reputationFactionIn |
P61188
|
FINISHED |
| Object | World of Warcraft |
—
|
NE NERFINISHED |
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: World of Warcraft | Statement: [The Shado-Pan, reputationFactionIn, World of Warcraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reputationFactionIn Context triple: [The Shado-Pan, reputationFactionIn, World of Warcraft]
-
A.
tacticalReputation
Indicates the perceived level of skill, reliability, or effectiveness an entity has in planning and executing tactics within a given context.
-
B.
clanReputation
Indicates the perceived status or esteem a clan holds within a community or among other clans based on its actions or history.
-
C.
hasReputationAmong
chosen
Indicates that an entity is regarded or perceived in a particular way by a specified group or audience.
-
D.
encounterReputation
Indicates a relationship where an entity’s reputation is affected or characterized by a particular encounter or interaction.
-
E.
reputationInLore
Indicates how an entity is regarded or reputed within a fictional or narrative lore context.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:19 p.m.