Triple
T37194882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Defense of the Ancients |
E921563
|
entity |
| Predicate | usesGameEngineOf |
P159886
|
FINISHED |
| Object | Warcraft III |
—
|
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: Warcraft III | Statement: [Defense of the Ancients, usesGameEngineOf, Warcraft III]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesGameEngineOf Context triple: [Defense of the Ancients, usesGameEngineOf, Warcraft III]
-
A.
supportsGameEngine
Indicates that one entity provides compatibility, functionality, or resources necessary for the operation or integration of a particular game engine.
-
B.
gameEngineUsage
chosen
Indicates that one entity (such as a project or product) uses or is built upon a particular game engine.
-
C.
notableGameEngineUse
Indicates that an entity is notably or prominently used as a game engine for another entity (such as a game or project).
-
D.
gameEngineType
Indicates the type or category of game engine associated with or used by an entity.
-
E.
notableGameEngineFor
Indicates that a particular game engine is especially recognized or significant for developing or powering a given game or set of games.
- 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_69f76ea313a08190a54404cd1e47da90 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.