Triple
T15135373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internet in Nepal |
E361539
|
entity |
| Predicate | urbanRuralGap |
P40698
|
FINISHED |
| Object | significant digital divide |
—
|
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: significant digital divide | Statement: [Internet in Nepal, urbanRuralGap, significant digital divide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanRuralGap Context triple: [Internet in Nepal, urbanRuralGap, significant digital divide]
-
A.
urbanRuralSplit
chosen
Indicates a division or distinction between urban and rural areas, conditions, or populations.
-
B.
isRuralOrUrban
Indicates whether an entity is classified as being in a rural area or an urban area.
-
C.
isLessUrbanizedThan
Indicates that one place has a lower degree of urban development or urban characteristics compared to another place.
-
D.
urbanizationLevel
Indicates the degree to which an area or population is characterized by urban development, infrastructure, and density of human settlement.
-
E.
urbanStatusContext
Indicates the relationship between an entity and the urban characteristics or conditions of its surrounding environment or context.
- 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005b3f6f48190b1ed7c7b28feb7a6 |
completed | April 15, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69deb9713fe881909dec2fd3f6c84b39 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:07 a.m.