Triple
T27569884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solu |
E696002
|
entity |
| Predicate | regionTypeWithinSolukhumbu |
P187028
|
FINISHED |
| Object | lower Solukhumbu |
—
|
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: lower Solukhumbu | Statement: [Solu, regionTypeWithinSolukhumbu, lower Solukhumbu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionTypeWithinSolukhumbu Context triple: [Solu, regionTypeWithinSolukhumbu, lower Solukhumbu]
-
A.
bordersAdministrativeRegionOfNepal
Indicates that one administrative region of Nepal shares a common boundary with another administrative region of Nepal.
-
B.
distanceFromKathmandu
Indicates the measured spatial distance between a given location or entity and the city of Kathmandu.
-
C.
distanceToNepalgunj_km
Indicates the physical distance, measured in kilometers, between a given location and Nepalgunj.
-
D.
borderingBhutaneseDistricts
Indicates that the specified Bhutanese districts share a common boundary with each other.
-
E.
entryPointFromNepal
Indicates that something serves as an entry point or access route originating from Nepal.
- 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_69ef53891af88190a193c5e2a1dac9b1 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb3424724c8190ba55ecf66fa0b171 |
completed | May 6, 2026, 12:29 p.m. |
Created at: April 27, 2026, 1:43 p.m.