Triple
T36963479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dust District |
E914365
|
entity |
| Predicate | hasCombatEncounters |
P73817
|
FINISHED |
| Object | Howlers vs Overseers skirmishes |
—
|
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: Howlers vs Overseers skirmishes | Statement: [Dust District, hasCombatEncounters, Howlers vs Overseers skirmishes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCombatEncounters Context triple: [Dust District, hasCombatEncounters, Howlers vs Overseers skirmishes]
-
A.
sawCombatAgainst
Indicates that one entity directly engaged in combat or battle against another entity.
-
B.
sawCombat
Indicates that an entity directly participated in active military or armed conflict.
-
C.
sawCombatInRegion
Indicates that an entity participated in combat operations within a specified geographic region.
-
D.
hasCombat
chosen
Indicates that an entity engages in, is involved with, or possesses the capability for combat or fighting interactions with other entities.
-
E.
battledIn
Indicates that two or more entities engaged in a battle or conflict that took place at a specific location or during a particular event.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.