Triple
T25379886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District 230 |
E631355
|
entity |
| Predicate | isConsolidatedDistrict |
P160118
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [District 230, isConsolidatedDistrict, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isConsolidatedDistrict Context triple: [District 230, isConsolidatedDistrict, true]
-
A.
isSingleDistrictFor
Indicates that one district uniquely and exclusively serves or applies to a given entity, with no other districts sharing that role.
-
B.
hasMunicipalConsolidationWith
Indicates that two or more municipalities have been officially merged or unified into a single administrative entity or structure.
-
C.
hasConsolidatedCityCountySince
Indicates that a city and county have been formally consolidated into a single unified government entity starting from a specified point in time.
-
D.
isNonMultiMemberDistrict
Indicates that an electoral district is represented by only a single member rather than multiple members.
-
E.
consolidatedJurisdictionOf
Indicates that legal authority or control over multiple areas or cases has been combined and is exercised under a single jurisdiction.
- F. None of above. chosen
Provenance (4 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_69e75a8c50788190aabaa9f96710fc43 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f6018f91248190985323d1a678e539 |
completed | May 2, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f5ffc6268c8190b63f6360ebadab73 |
completed | May 2, 2026, 1:44 p.m. |
Created at: April 21, 2026, 1:46 p.m.