Triple
T20723744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Debaltseve |
E509381
|
entity |
| Predicate | preWarFunction |
P120520
|
FINISHED |
| Object | industrial and transport center |
—
|
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: industrial and transport center | Statement: [Debaltseve, preWarFunction, industrial and transport center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preWarFunction Context triple: [Debaltseve, preWarFunction, industrial and transport center]
-
A.
postWarFunction
Indicates how something operated, was used, or what role it served in the period following a war.
-
B.
preWarServiceArea
Indicates the geographic area or jurisdiction in which an entity operated or provided service before a specified war or conflict.
-
C.
preWarContinuityWith
Indicates that a relationship, structure, or condition remains consistent with or directly continues from its state before a war or major conflict.
-
D.
prewarStatus
Indicates the condition, role, or circumstances of an entity as they existed before a specific war or armed conflict.
-
E.
preWarRole
chosen
Indicates the role, position, or function an entity held before the onset of a specified war or conflict.
- 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_69e0b4c4cc648190b45fda6e2b20af56 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1e59b2081909fb6c29cb5018bb4 |
completed | April 21, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69e5c04b31248190b9b9d91b5cb854e3 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:28 p.m.