Triple
T15088119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stuart Fenegan |
E360336
|
entity |
| Predicate | roleInWarcraft |
P117259
|
FINISHED |
| Object | producer |
—
|
LITERAL 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: producer | Statement: [Stuart Fenegan, roleInWarcraft, producer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInWarcraft Context triple: [Stuart Fenegan, roleInWarcraft, producer]
-
A.
roleInShadowlands
Indicates that one entity has a specific function, position, or significance within the context of the Shadowlands.
-
B.
roleInDiablo
Indicates the specific function, position, or character type an entity has within the context of the Diablo game series.
-
C.
relatedClassInWarcraft
Indicates that two entities are related through a class association within the Warcraft universe, such as sharing, corresponding to, or being mapped between specific Warcraft character classes.
-
D.
roleInLegendarium
Indicates that one entity serves a particular narrative or functional role within the fictional mythos or legendarium associated with another entity.
-
E.
roleInWarOfTheRing
Indicates the specific function, position, or involvement an entity had within the events of the War of the Ring.
- F. None of above. chosen
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_69d85a035aa88190b52a139d3a1b7b6d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00276d1608190bc310d5b86ecd1d5 |
completed | April 15, 2026, 9:26 p.m. |
| PD | Predicate disambiguation | batch_69deb9645b9c8190a5712456dbd78029 |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec71e8dcc81908badc834b6ccf273 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:03 a.m.