Triple
T38643807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allied Races |
E938666
|
entity |
| Predicate | unlockMethodChangedIn |
P188267
|
FINISHED |
| Object | World of Warcraft: Dragonflight |
—
|
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: Dragonflight | Statement: [Allied Races, unlockMethodChangedIn, World of Warcraft: Dragonflight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unlockMethodChangedIn Context triple: [Allied Races, unlockMethodChangedIn, World of Warcraft: Dragonflight]
-
A.
unlockBehavior
Indicates that one entity enables access to or activates the behavior, functionality, or state of another entity.
-
B.
unlockType
chosen
Indicates the method or condition by which access to something is unlocked or made available.
-
C.
unlocksAccessTo
Indicates that one entity enables or grants entry, permission, or availability to another entity, typically by removing a restriction or barrier.
-
D.
lockedMeans
Indicates that one state, condition, or action guarantees or necessitates another, such that when the first is "locked in," the second must follow.
-
E.
canUnlock
Indicates that one entity has the ability or permission to unlock another entity.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 3, 2026, 4:32 p.m.