Triple
T38179211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Local Government Area of Nigeria |
E1005105
|
entity |
| Predicate | hasRevenuePowers |
P50971
|
FINISHED |
| Object | collection of local taxes and rates |
—
|
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: collection of local taxes and rates | Statement: [Local Government Area of Nigeria, hasRevenuePowers, collection of local taxes and rates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRevenuePowers Context triple: [Local Government Area of Nigeria, hasRevenuePowers, collection of local taxes and rates]
-
A.
haveFiscalPowers
chosen
Indicates that an entity possesses legal authority or control over financial or budgetary matters.
-
B.
hasPower
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
-
C.
hasOperationalPowers
Indicates that an entity possesses the authority or capability to perform specific operational actions or functions.
-
D.
hasPowerPositions
Indicates that one entity holds influential or authoritative roles or positions within another entity or context.
-
E.
hasNumberOfPowers
Indicates the quantity of distinct powers or abilities that an entity possesses.
- 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_69f76dbc22c481908139b694ffde7a0c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:29 p.m.