Triple
T29167707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District 1 Council seat |
E739365
|
entity |
| Predicate | belongsToDistrictNumber |
P13282
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [District 1 Council seat, belongsToDistrictNumber, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToDistrictNumber Context triple: [District 1 Council seat, belongsToDistrictNumber, 1]
-
A.
belongsToDistrictLevelCity
Indicates that an entity is administratively part of, or falls under the jurisdiction of, a specific district-level city.
-
B.
communityDistrictNumber
chosen
Indicates the specific community district identifier associated with an entity or location.
-
C.
hasDistrictPart
Indicates that one administrative or geographic entity includes another entity as a district-level subdivision or component.
-
D.
containsDistrictMunicipality
Indicates that an administrative region includes one or more district municipalities within its boundaries.
-
E.
basedInDistrict
Indicates that an entity is located or has its primary base of operations within a specific administrative 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_69f07cb6394c8190ab7842c48e699e2a |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: April 28, 2026, 11:50 a.m.