Triple
T24414167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bajura District |
E615535
|
entity |
| Predicate | developmentFocusAreas |
P129848
|
FINISHED |
| Object | infrastructure development |
—
|
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: infrastructure development | Statement: [Bajura District, developmentFocusAreas, infrastructure development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developmentFocusAreas Context triple: [Bajura District, developmentFocusAreas, infrastructure development]
-
A.
developmentFocusedOn
Indicates that the primary effort or activity of development is directed toward a specific target, aspect, or objective.
-
B.
developmentDirection
Indicates the primary orientation or path along which something grows, progresses, or evolves over time.
-
C.
deploymentFocus
Indicates the primary area, target, or aspect that a deployment is directed toward or concentrated on.
-
D.
hasDevelopmentFocus
chosen
Indicates that an entity is primarily concerned with or directed toward a particular area, goal, or aspect of development.
-
E.
developmentArea
Indicates the geographic or conceptual region within which development, construction, or growth activities are planned, permitted, or occurring.
- 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_69e2d7e9bfac8190a748952a90957106 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29583c2688190af3bc5d02eb9a3d9 |
completed | April 29, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:12 a.m.