Triple
T11541942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World of Warcraft: Warlords of Draenor |
E273694
|
entity |
| Predicate | featureIntroduced |
P82895
|
FINISHED |
| Object | garrisons |
—
|
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: garrisons | Statement: [World of Warcraft: Warlords of Draenor, featureIntroduced, garrisons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featureIntroduced Context triple: [World of Warcraft: Warlords of Draenor, featureIntroduced, garrisons]
-
A.
featureAdded
chosen
Indicates that a new feature has been introduced or incorporated into a system, product, or entity.
-
B.
introducedFeatureCategory
Indicates that an entity caused a particular feature category to be created, presented, or made available for the first time.
-
C.
laterFeature
Indicates that one feature, event, or element occurs or is introduced after another in time.
-
D.
serviceIntroduced
Indicates that a particular service has been launched, made available, or brought into operation at a certain time or context.
-
E.
developmentFeature
Indicates that one entity serves as a developmental feature, aspect, or component of another entity within a growth or improvement process.
- 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.