Triple
T16299616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tobago House of Assembly |
E395748
|
entity |
| Predicate | hasNumberOfElectoralDistricts |
P13200
|
FINISHED |
| Object | 12 |
—
|
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: 12 | Statement: [Tobago House of Assembly, hasNumberOfElectoralDistricts, 12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfElectoralDistricts Context triple: [Tobago House of Assembly, hasNumberOfElectoralDistricts, 12]
-
A.
hasElectoralDistricts
Indicates that a political or administrative unit is divided into one or more electoral districts used for representation or voting.
-
B.
hasNumberOfConstituencies
chosen
Indicates the specific count of constituencies associated with an entity.
-
C.
hasNumberOfStatesAndDistricts
Indicates a relationship where an entity is associated with a specific count of its constituent states and districts.
-
D.
hasParallelElectorates
Indicates that two electoral systems or jurisdictions share corresponding or equivalent electorates that function in parallel.
-
E.
hasElectoralUnit
Indicates that a political or administrative entity is associated with a specific electoral unit used for voting or representation.
- 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e25e31c9e8819094593f3aeb44f2ca |
completed | April 17, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69e219fa5508819097e9d383348bf174 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.