Triple
T31743317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naxalbari |
E810195
|
entity |
| Predicate | borderingCountryProximity |
P17986
|
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: [Naxalbari, borderingCountryProximity, Nepal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderingCountryProximity Context triple: [Naxalbari, borderingCountryProximity, Nepal]
-
A.
countryBorderProximity
chosen
Indicates that one country is geographically close to or directly bordering another country.
-
B.
borderingCountryNearby
Indicates that one country is geographically close to, but does not necessarily share a direct land border with, another country.
-
C.
nearFirstNationsTerritory
Indicates that one entity is located close to, but not necessarily within, the territory traditionally or legally associated with a First Nations group.
-
D.
borderingCountryContext
Indicates that one country shares a land or maritime boundary with another within a specified geopolitical or temporal context.
-
E.
nearFormerBorderWith
Indicates that one entity is located close to where the former border or boundary with another entity used to be.
- 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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69feced53a7c819098ec474fb7d514b0 |
completed | May 9, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69fecd9cd5288190aac8b4e04a7ee78e |
completed | May 9, 2026, 6:01 a.m. |
Created at: April 30, 2026, 11:25 p.m.