Triple
T11541878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World of Warcraft: The Burning Crusade |
E273693
|
entity |
| Predicate | introducedProfession |
P69514
|
FINISHED |
| Object | Jewelcrafting |
—
|
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: Jewelcrafting | Statement: [World of Warcraft: The Burning Crusade, introducedProfession, Jewelcrafting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedProfession Context triple: [World of Warcraft: The Burning Crusade, introducedProfession, Jewelcrafting]
-
A.
memberProfession
Indicates that a member or individual holds or practices a particular profession or occupation.
-
B.
includesProfession
chosen
Indicates that one entity’s set of attributes, roles, or members contains a specific profession as part of it.
-
C.
recognizesProfession
Indicates that one entity acknowledges or identifies another entity’s professional role or occupation as such.
-
D.
isAssociatedWithProfessionOfBearer
Indicates that one entity is connected to, or involved with, the profession or occupational role held by another entity.
-
E.
portraysProfession
Indicates that one entity depicts or represents another entity in a specific profession or occupational role.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e09eec8190894069d86b79183d |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d80879fdb48190be6dacc8aa63c809 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.