Triple
T37461143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cho'gall |
E930918
|
entity |
| Predicate | gameRoleInHearthstone |
P187928
|
FINISHED |
| Object | legendary card |
—
|
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: legendary card | Statement: [Cho'gall, gameRoleInHearthstone, legendary card]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameRoleInHearthstone Context triple: [Cho'gall, gameRoleInHearthstone, legendary card]
-
A.
roleInWarcraft
Indicates that an entity has a specific character, class, or functional role within the Warcraft universe or game setting.
-
B.
gameRoleForPlayers
Indicates the specific role or function that players have within a particular game or gameplay context.
-
C.
roleAtRagnarok
Indicates the specific function, position, or part an entity is expected to have or perform during Ragnarok.
-
D.
roleInShadowlands
Indicates that one entity has a specific function, position, or significance within the context of the Shadowlands.
-
E.
showdown!Role
Indicates a role or function that an entity assumes or performs within the context of a showdown or competitive confrontation.
- 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.