Triple
T16872340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orenburg Oblast |
E421200
|
entity |
| Predicate | borderLengthWithKazakhstan |
P57957
|
FINISHED |
| Object | long land border |
—
|
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: long land border | Statement: [Orenburg Oblast, borderLengthWithKazakhstan, long land border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderLengthWithKazakhstan Context triple: [Orenburg Oblast, borderLengthWithKazakhstan, long land border]
-
A.
borderTypeWithTurkmenistan
Indicates the type or nature of the border relationship that an entity has with Turkmenistan.
-
B.
borderTypeWithMongolia
Indicates the specific nature or classification of the border that an entity shares with Mongolia.
-
C.
shareLandBorderLengthApproxKm
chosen
Indicates that two entities share a land border whose length is approximately the given number of kilometers.
-
D.
borderTypeWithArmenia
Indicates the type or nature of the border relationship that an entity has with Armenia.
-
E.
distanceToRussianBorder_km
Indicates the physical distance, measured in kilometers, between a given location and the nearest point on the Russian border.
- 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_69d889d470fc8190b4aec199636c0c56 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3b7f31b448190a21e3e4d1a0d2f73 |
completed | April 18, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69e32b90ec3c819099c51bb7baf2984c |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:29 a.m.