Triple
T4298203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ural Cossack forces |
E99767
|
entity |
| Predicate | borderGuardFunction |
P33937
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Ural Cossack forces, borderGuardFunction, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderGuardFunction Context triple: [Ural Cossack forces, borderGuardFunction, yes]
-
A.
borderControls
Indicates that one entity enforces or administers border control measures over another entity or at a specific boundary.
-
B.
borderStation
Indicates a facility or checkpoint located at or near a border where cross-boundary movement, control, or processing of people or goods occurs.
-
C.
borderControlSide
Indicates that one entity is positioned on or associated with a particular side or segment of a border control area or checkpoint.
-
D.
hasBorderGuardingMandateWith
chosen
Indicates that one entity has an official responsibility or mandate to guard, monitor, or secure a border in cooperation or association with another entity.
-
E.
borderMonitored
Indicates that a border between two regions or entities is actively being watched, controlled, or surveilled.
- 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_69b3455175088190aa79c6e03b86647e |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3509bff808190a86fade7ccfc3611 |
completed | March 12, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69b347fe55a88190b77bab0c0f38e1aa |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:08 p.m.