Triple
T30225498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarpang District |
E768466
|
entity |
| Predicate | hasGewog |
P183502
|
FINISHED |
| Object | Gelephu Gewog |
—
|
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: Gelephu Gewog | Statement: [Sarpang District, hasGewog, Gelephu Gewog]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGewog Context triple: [Sarpang District, hasGewog, Gelephu Gewog]
-
A.
hasUpazila
Indicates a relationship where a larger administrative region or district includes or is associated with one or more upazilas (sub-districts).
-
B.
hasGmina
Indicates that an entity is administratively associated with, or belongs to, a specific gmina (a basic local government unit/municipality).
-
C.
hasTehsil
Indicates a relationship where an administrative region or district includes or is associated with a specific tehsil (sub-district) within its jurisdiction.
-
D.
hasVillage
Indicates that an entity possesses, contains, or is associated with a village.
-
E.
isVillageDistrictOf
Indicates that one administrative unit is a village-level district that belongs to or is governed by a larger territorial entity.
- 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_69f2248108208190be60bf1af343ce70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7a01efcc08190bba489a9099b8684 |
completed | May 3, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79f477c4c8190a35cb6d87b1dcbd1 |
completed | May 3, 2026, 7:17 p.m. |
Created at: April 29, 2026, 7:35 p.m.