Triple
T1368703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 163rd Rifle Division |
E30060
|
entity |
| Predicate | logisticalIssue |
P10774
|
FINISHED |
| Object | severe supply problems in winter conditions |
—
|
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: severe supply problems in winter conditions | Statement: [163rd Rifle Division, logisticalIssue, severe supply problems in winter conditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: logisticalIssue Context triple: [163rd Rifle Division, logisticalIssue, severe supply problems in winter conditions]
-
A.
logistics
chosen
Indicates the organization, coordination, and management of how resources, goods, or information are efficiently moved and handled between entities.
-
B.
facingIssue
Indicates that an entity is currently experiencing, encountering, or dealing with a problem, difficulty, or obstacle.
-
C.
underlyingIssue
Indicates that one situation, problem, or condition is the fundamental cause or root problem behind another.
-
D.
knownIssue
Indicates that the subject has an issue or problem that is already identified, recognized, or documented.
-
E.
addressesIssue
Indicates that one entity deals with, responds to, or attempts to resolve a specific issue associated with another entity.
- 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_69a498f912008190a376a98b207b2071 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c2d497f88190993d16a208ced43d |
completed | March 1, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69a4befb08b88190be966fa1aadd4bcd |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:57 p.m.