Triple
T27349170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiev Voivodeship |
E684308
|
entity |
| Predicate | frontierWith |
P165704
|
FINISHED |
| Object | Crimean Khanate |
—
|
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: Crimean Khanate | Statement: [Kiev Voivodeship, frontierWith, Crimean Khanate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontierWith Context triple: [Kiev Voivodeship, frontierWith, Crimean Khanate]
-
A.
frontierSystem
Indicates a system that lies at or near the boundary or edge of a defined region, domain, or area of control.
-
B.
frontierImplication
Indicates that one condition or state at a boundary or limit logically leads to, constrains, or entails another condition or state at that boundary.
-
C.
northernFrontier
Indicates that one entity serves as the northern boundary, edge, or frontier region relative to another entity.
-
D.
wasFrontierBetween
Indicates that one entity historically served as the boundary or border region separating two other entities.
-
E.
nearbyFrontier
Indicates that one entity is located close to a boundary or frontier region associated with another entity.
- 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65a6babcc81908052c9907a99c882 |
completed | May 2, 2026, 8:11 p.m. |
Created at: April 27, 2026, 11:47 a.m.