Triple
T17700985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Панҷ |
E441297
|
entity |
| Predicate | используетсяКакГраница |
P91946
|
FINISHED |
| Object | межгосударственная граница |
—
|
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: межгосударственная граница | Statement: [Панҷ, используетсяКакГраница, межгосударственная граница]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: используетсяКакГраница Context triple: [Панҷ, используетсяКакГраница, межгосударственная граница]
-
A.
usedAsBorder
chosen
Indicates that one entity functions as a boundary or dividing line for another entity.
-
B.
isBoundaryFor
Indicates that one entity serves as the limiting edge, border, or enclosing extent that defines the spatial or conceptual bounds of another entity.
-
C.
borderArea
Indicates that an area lies along or near the boundary between two regions, countries, or territories.
-
D.
borderSectionOf
Indicates that one entity represents a specific segment or portion of the overall border of another entity.
-
E.
setsBoundary
Indicates that one entity defines or forms the limiting edge or border of another 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_69d8b9ea20b48190ace88bb46b01e6a9 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4715ae1fc81908438a1bba970c6ec |
completed | April 19, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69e3cde601d4819097903f471f1fe99a |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:04 a.m.