Triple
T31697893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Sea Cossacks |
E808963
|
entity |
| Predicate | borderGuardDuty |
P198142
|
FINISHED |
| Object | Ottoman Empire frontier |
—
|
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: Ottoman Empire frontier | Statement: [Black Sea Cossacks, borderGuardDuty, Ottoman Empire frontier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderGuardDuty Context triple: [Black Sea Cossacks, borderGuardDuty, Ottoman Empire frontier]
-
A.
borderMonitored
Indicates that a border between two regions or entities is actively being watched, controlled, or surveilled.
-
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.
borderStationFor
Indicates that a particular border station serves, monitors, or is responsible for a specific border crossing or boundary segment.
-
D.
borderControls
Indicates that one entity enforces or administers border control measures over another entity or at a specific boundary.
-
E.
borderControlSide
Indicates that one entity is positioned on or associated with a particular side or segment of a border control area or checkpoint.
- 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fecd0a732c819097bdd3eb69b6158c |
completed | May 9, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69fecc0318d481908b5b20598a76a9fe |
completed | May 9, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69fecd091abc8190872974de731a80fa |
completed | May 9, 2026, 5:58 a.m. |
Created at: April 30, 2026, 11:11 p.m.