Triple
T37460282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grobbulus |
E930899
|
entity |
| Predicate | originallyFromContent |
P22683
|
FINISHED |
| Object | World of Warcraft classic Naxxramas level 60 raid |
E944675
|
NE 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: World of Warcraft classic Naxxramas level 60 raid | Statement: [Grobbulus, originallyFromContent, World of Warcraft classic Naxxramas level 60 raid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyFromContent Context triple: [Grobbulus, originallyFromContent, World of Warcraft classic Naxxramas level 60 raid]
-
A.
primaryContentOrigin
Indicates that one entity is the main or original source from which the content of another entity is derived.
-
B.
hasContentFrom
chosen
Indicates that one entity’s content is derived from, includes, or is based on another entity.
-
C.
originallyBy
Indicates that one entity is the original creator, author, or source of another entity.
-
D.
originallyIn
Indicates that something first appeared, was created, or was initially located within a particular context, source, or place.
-
E.
originatesAs
Indicates that one entity begins, arises, or comes into existence in the form, state, or role specified by another entity.
- F. None of above.
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_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a408c2fd1008190b1d22ac3d5ae05a0 |
completed | June 28, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.