Triple
T8728755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indo-Nepal border |
E207197
|
entity |
| Predicate | hasBorderLength |
P39383
|
FINISHED |
| Object | approximately 1850 km |
—
|
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: approximately 1850 km | Statement: [Indo-Nepal border, hasBorderLength, approximately 1850 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderLength Context triple: [Indo-Nepal border, hasBorderLength, approximately 1850 km]
-
A.
hasBorderLengthCharacteristic
chosen
Indicates that a border is associated with a specific length-related property or characteristic.
-
B.
hasBorderElement
Indicates that one entity includes or is associated with another entity that forms part of its boundary or edge.
-
C.
hasBorderDirection
Indicates that one entity’s border lies in, or is oriented toward, a specified cardinal or relative direction with respect to another entity.
-
D.
hasBorderTerminus
Indicates that one entity serves as the endpoint or terminal location of another entity’s border or boundary.
-
E.
hadBorderType
Indicates that a boundary between two entities existed and specifies the nature or classification of that border (e.g., land, maritime, disputed).
- 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_69ca8358e4008190898471a59b96c301 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d19fdc88190860e0c9c93ab79ce |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc457093188190959287a6458651c6 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:37 p.m.