Triple
T37463947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warrior |
E930986
|
entity |
| Predicate | wowRole |
P187954
|
FINISHED |
| Object | tank (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: tank (World of Warcraft) | Statement: [Warrior, wowRole, tank (World of Warcraft)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wowRole Context triple: [Warrior, wowRole, tank (World of Warcraft)]
-
A.
winnerRole
Indicates the role or position held by the entity that is the winner in a given event or competition.
-
B.
roleInWZRD
Indicates that an entity holds a specific role or function within the context of WZRD.
-
C.
wrestlingRole
Indicates the specific capacity or function an individual performs within a wrestling context, such as competitor, referee, coach, or other defined role.
-
D.
peakRole
Indicates the role or position an entity holds at the highest or most prominent point of its activity, status, or performance.
-
E.
role
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fb92ee27408190b0116ef2d789abac |
completed | May 6, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:17 p.m.