Triple
T20245083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Debaltseve pocket |
E498402
|
entity |
| Predicate | peakFighting |
P139381
|
FINISHED |
| Object | January 2015 |
—
|
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: January 2015 | Statement: [Debaltseve pocket, peakFighting, January 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakFighting Context triple: [Debaltseve pocket, peakFighting, January 2015]
-
A.
fightingPreference
Indicates a relationship where one entity has a favored way, style, or choice of engaging in fights or combat relative to others.
-
B.
fightingOutOf
Indicates that an individual is competing or representing themselves in a fight or match while being officially associated with a particular location, camp, or organization.
-
C.
fightsUsing
Indicates that one entity engages in combat or conflict by employing another entity as its weapon, tool, or method of fighting.
-
D.
strengthPeak
Indicates the point or period at which an entity’s strength reaches its maximum level.
-
E.
diesFighting
Indicates that an entity dies as a direct result of engaging in a fight or combat.
- 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_69da6274c58c81909c646eabed6f4f30 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e673a10ab48190a408a5d2c2b0808b |
completed | April 20, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69e55b1b23f88190bdcbe2f81dd226dd |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:40 p.m.