Triple
T36358296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hostomel |
E895409
|
entity |
| Predicate | occupantDuringConflict |
P129215
|
FINISHED |
| Object | Russian Armed Forces |
—
|
NE NERFINISHED |
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: Russian Armed Forces | Statement: [Hostomel, occupantDuringConflict, Russian Armed Forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occupantDuringConflict Context triple: [Hostomel, occupantDuringConflict, Russian Armed Forces]
-
A.
occupants
Indicates that certain entities are currently inhabiting, residing in, or using a particular place, space, or object.
-
B.
stanceDuringConflict
Indicates the position, attitude, or side an entity adopts in relation to a specific conflict or dispute.
-
C.
heldDuringConflict
chosen
Indicates that an entity maintained control, possession, or occupation of something for some duration while an identified conflict was ongoing.
-
D.
allyInConflict
Indicates that one entity supports and cooperates with another entity as an ally within the context of a specific conflict or dispute.
-
E.
conflictParticipantIn
Indicates that an entity takes part as a participant in a specific conflict or dispute.
- 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_69f76e5044248190b390d8887dc03254 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:09 p.m.