Triple
T27349169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiev Voivodeship |
E684308
|
entity |
| Predicate | wasFrontierProvince |
P84933
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Kiev Voivodeship, wasFrontierProvince, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasFrontierProvince Context triple: [Kiev Voivodeship, wasFrontierProvince, true]
-
A.
wasFrontierRegion
chosen
Indicates that a region historically functioned as a frontier area, marking a boundary or border zone between larger political or cultural entities.
-
B.
wasFrontierBetween
Indicates that one entity historically served as the boundary or border region separating two other entities.
-
C.
laterProvince
Indicates that one administrative region or province succeeds another in time, coming into existence or effect after the other.
-
D.
northernFrontier
Indicates that one entity serves as the northern boundary, edge, or frontier region relative to another entity.
-
E.
wasCoreTerritoryOf
Indicates that a region historically formed the central or most important territorial area belonging to a particular political or cultural entity.
- 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f62ba5a110819092fe773ade8fec2e |
completed | May 2, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69f620e4b1c88190a17940251abc68fd |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 11:47 a.m.