Triple
T38592125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scarab Wall |
E932477
|
entity |
| Predicate | firstOpenedInExpansion |
P100003
|
FINISHED |
| Object | World of Warcraft (classic) |
E279291
|
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) | Statement: [Scarab Wall, firstOpenedInExpansion, World of Warcraft (classic)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstOpenedInExpansion Context triple: [Scarab Wall, firstOpenedInExpansion, World of Warcraft (classic)]
-
A.
introducedExpansion
Indicates that an entity caused a new expansion, extension, or enlargement of something to be brought into existence or put into use.
-
B.
introducedInExpansion
chosen
Indicates that something (such as a feature, item, or concept) was first added or made available as part of a specific expansion.
-
C.
firstOpenedAt
Indicates the date and time at which something was initially opened for the first time.
-
D.
restoredInExpansion
Indicates that something previously removed or absent was brought back or made available again as part of an expansion.
-
E.
appearsInGameExpansion
Indicates that an entity is featured or included within a specific game expansion.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a47497b998c81908dec1bfa6082f17c |
completed | July 3, 2026, 5:32 a.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.