Triple
T24279272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurram |
E605493
|
entity |
| Predicate | localGovernanceRole |
P81461
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Kurram, localGovernanceRole, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localGovernanceRole Context triple: [Kurram, localGovernanceRole, yes]
-
A.
hasLocalGovernanceRole
chosen
Indicates that an entity holds an official position or responsibility within a local or municipal governing body.
-
B.
districtRole
Indicates that an entity holds a specific role, function, or position within a particular district.
-
C.
hasLocalGovernanceType
Indicates the specific form or system of local governance that applies to an entity.
-
D.
hasLocalGovernanceUnit
Indicates that an entity is administered or overseen by a specific local governance unit, such as a municipality, district, or similar subnational authority.
-
E.
governsRoleOf
Indicates that one entity has authority or control over the role, responsibilities, or functions assigned to 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_69e2954707dc8190915551eb114cfff6 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f5032f48190a027e2d8b382ee79 |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:07 a.m.