Triple
T15407277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nasarawa State House of Assembly |
E368491
|
entity |
| Predicate | hasLawMakingPower |
P2844
|
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: [Nasarawa State House of Assembly, hasLawMakingPower, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLawMakingPower Context triple: [Nasarawa State House of Assembly, hasLawMakingPower, yes]
-
A.
hasLegislativePower
chosen
Indicates that an entity possesses the authority to create, amend, or repeal laws within a given jurisdiction or governing framework.
-
B.
hasRegulatoryPower
Indicates that one entity possesses formal authority to create, enforce, or oversee rules and regulations governing another entity or activity.
-
C.
hasStatePowers
Indicates that an entity possesses or exercises the official powers or authorities of a state-level government.
-
D.
hasLegislatureType
Indicates the specific form or system of legislature that an entity possesses or operates under.
-
E.
promulgatesLawsAt
Indicates the action by which an authority formally enacts or issues laws within a particular jurisdiction or location.
- 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_69d85a16c68c819099c1b547fbc87b32 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03ea36c6881909eaea48e9608897a |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27b8cac8190bfa77698d53c5d1c |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:20 a.m.