Triple
T37458357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Murloc Shaman |
E930854
|
entity |
| Predicate | mulliganPriority |
P126612
|
FINISHED |
| Object | Cheap Murloc minions |
—
|
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: Cheap Murloc minions | Statement: [Murloc Shaman, mulliganPriority, Cheap Murloc minions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mulliganPriority Context triple: [Murloc Shaman, mulliganPriority, Cheap Murloc minions]
-
A.
priorityRule
chosen
Indicates that one entity is given precedence or higher processing order over another according to a defined rule or policy.
-
B.
missionPriority
Indicates the relative level of importance or urgency assigned to a mission compared to other missions or tasks.
-
C.
limitsPriorityOf
Indicates that one entity imposes a maximum allowable priority level on another entity’s priority.
-
D.
priorityDeterminedBy
Indicates that the priority or importance level of one entity is established based on another entity or set of factors.
-
E.
managementPriority
Indicates the relative level of importance or urgency assigned to managing or addressing a particular entity, issue, or task.
- 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_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. |
Created at: May 3, 2026, 4:17 p.m.