Triple
T17700986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Панҷ |
E441297
|
entity |
| Predicate | типГраницы |
P1972
|
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.
typicalBoundary
Indicates that one entity serves as the usual or characteristic boundary or limit for another entity.
-
B.
hasBoundaryType
chosen
Indicates that one entity has a boundary characterized by a specific type or classification in relation to another entity or context.
-
C.
bordureType
Indicates the specific style or pattern used for the border or edging of an item or area.
-
D.
dimensionBoundType
Indicates the type or nature of the constraint that bounds a given dimension in a relationship.
-
E.
formsPartOfBorderType
Indicates that one border type constitutes a component or segment of another, more comprehensive border type.
- 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.