Triple
T2360958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zakatal Okrug |
E47268
|
entity |
| Predicate | borderCharacteristic |
P38214
|
FINISHED |
| Object | frontier district of the Russian Empire |
—
|
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: frontier district of the Russian Empire | Statement: [Zakatal Okrug, borderCharacteristic, frontier district of the Russian Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderCharacteristic Context triple: [Zakatal Okrug, borderCharacteristic, frontier district of the Russian Empire]
-
A.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
-
B.
borderDefinedBy
Indicates that the boundary or limit of one entity is determined, shaped, or delineated by another entity.
-
C.
borderStraddling
Indicates that something (such as a feature, structure, or area) extends across and occupies territory on both sides of a border between two regions or jurisdictions.
-
D.
borderSectionName
Indicates the specific named segment or portion of a border that is associated with or applies to an entity.
-
E.
borderColor
Indicates the color that forms the boundary or outline of an 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_69a88a1a4a6081908645b0f2914521ab |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc723c66481908a9b94991f651b3b |
completed | March 7, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69abc599b92c819093d9e15d4437705d |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abc6a85e2c8190afec217ff29476be |
completed | March 7, 2026, 6:33 a.m. |
Created at: March 4, 2026, 7:55 p.m.