Triple
T13669044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Elder Scrolls Online: Morrowind |
E327700
|
entity |
| Predicate | battlegroundType |
P111081
|
FINISHED |
| Object | Team Deathmatch |
—
|
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: Team Deathmatch | Statement: [The Elder Scrolls Online: Morrowind, battlegroundType, Team Deathmatch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battlegroundType Context triple: [The Elder Scrolls Online: Morrowind, battlegroundType, Team Deathmatch]
-
A.
battlefieldOf
Indicates that a location is the site where a particular battle or military engagement took place.
-
B.
wasKeyBattlegroundDuring
Indicates that a location served as an important site of conflict or struggle during a specified event or period.
-
C.
warfareType
Indicates the specific kind or category of warfare that characterizes a given conflict or military engagement.
-
D.
battlefieldFunction
Indicates the role or purpose an entity serves within a combat or battlefield context, such as its tactical or operational function during warfare.
-
E.
battleScale
Indicates the relative size or intensity of a battle, such as how large, extensive, or severe the conflict is.
- 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_69d8076f1fa8819094664a59b55010df |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc65832688190aea688fee0a7cbdb |
completed | April 12, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8d8d0881908d6e89954f44eed4 |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59ca1a88190a6abd3bd00554c93 |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 9:53 p.m.