Triple
T35793728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lion of Azeroth |
E1034765
|
entity |
| Predicate | metaOrigin |
P183676
|
FINISHED |
| Object | Blizzard Entertainment |
—
|
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: Blizzard Entertainment | Statement: [Lion of Azeroth, metaOrigin, Blizzard Entertainment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metaOrigin Context triple: [Lion of Azeroth, metaOrigin, Blizzard Entertainment]
-
A.
registrationOrigin
Indicates the source or context from which a registration event was initiated or created.
-
B.
alternativeOrigin
Indicates that an entity has a different or secondary source, starting point, or provenance compared to its primary or usual origin.
-
C.
holderOrigin
Indicates that one entity is the original source, creator, or origin point from which the holder entity derives, is issued, or established.
-
D.
originSite
Indicates the place or site from which something or someone originally comes or is derived.
-
E.
maskOrigin
Indicates that one entity serves as the original source or basis from which another entity’s mask or masking representation is derived.
- 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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a25368b0819087fd05a246bacc5f |
completed | May 3, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a162672481909773f8383d91159a |
completed | May 3, 2026, 7:26 p.m. |
Created at: May 3, 2026, 4:06 p.m.