Triple
T27527437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhaktapur Durbar Square |
E694871
|
entity |
| Predicate | localManagement |
P70706
|
FINISHED |
| Object | Bhaktapur Municipality |
—
|
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: Bhaktapur Municipality | Statement: [Bhaktapur Durbar Square, localManagement, Bhaktapur Municipality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localManagement Context triple: [Bhaktapur Durbar Square, localManagement, Bhaktapur Municipality]
-
A.
hasLocalManagement
chosen
Indicates that an entity is managed, administered, or overseen by an authority or management structure located within the same local area or jurisdiction.
-
B.
localBehavior
Indicates that a behavior or effect is determined primarily by nearby or immediate context rather than by distant or global factors.
-
C.
localStatus
Indicates the current condition or state of an entity within a specific local context or environment.
-
D.
sectorManaged
Indicates that one entity is responsible for administering, overseeing, or directing the operations of a particular sector.
-
E.
managementIs
Indicates that one entity holds a managerial role, responsibility, or authority over another entity.
- 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_69ef538550208190aa9de8e2cb260d93 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 1:24 p.m.