Triple
T27312508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandakphu |
E689245
|
entity |
| Predicate | hasBorderView |
P177110
|
FINISHED |
| Object | Nepal |
—
|
NE NERFINISHED |
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: Nepal | Statement: [Sandakphu, hasBorderView, Nepal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderView Context triple: [Sandakphu, hasBorderView, Nepal]
-
A.
hasBorderElement
Indicates that one entity includes or is associated with another entity that forms part of its boundary or edge.
-
B.
hasBorderRole
Indicates that an entity holds a specific functional or administrative role related to a border or boundary between regions or jurisdictions.
-
C.
hasOwnBorderControls
Indicates that an entity independently manages and enforces its own border control policies and procedures, separate from those of other entities.
-
D.
hasBorderDirection
Indicates that one entity’s border lies in, or is oriented toward, a specified cardinal or relative direction with respect to another entity.
-
E.
hasBorderSignificance
Indicates that a border between entities holds particular importance, impact, or relevance in a given context.
- 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_69ef355c53a08190a8a92e355a7ce115 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6f85bfba48190aba95b40642a8ca7 |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f854486c81909396d944a55e03ab |
completed | May 3, 2026, 7:25 a.m. |
Created at: April 27, 2026, 11:28 a.m.