Triple
T3327286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jigawa State |
E69944
|
entity |
| Predicate | hasSenatorialDistricts |
P21199
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Jigawa State, hasSenatorialDistricts, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSenatorialDistricts Context triple: [Jigawa State, hasSenatorialDistricts, 3]
-
A.
hasElectoralDistricts
Indicates that a political or administrative unit is divided into one or more electoral districts used for representation or voting.
-
B.
hasNumberOfSenatorialDivisions
chosen
Indicates the relationship that specifies how many senatorial divisions are associated with a given entity.
-
C.
hasUSSenator
Indicates that a specified state or jurisdiction is represented by a particular individual serving as a United States Senator.
-
D.
hasCouncilDistrict
Indicates that an entity is located within or represented by a specific council district.
-
E.
locatedInStateSenateDistrict
Indicates that one entity is geographically situated within the boundaries of a particular state senate legislative district.
- 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_69ad85a1829881908942c14075644d0d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb16f61248190bab10f4ac9e066f7 |
completed | March 8, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69ada42a19348190a3862ce02451f4aa |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:12 p.m.