Triple
T27569076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glenville |
E695980
|
entity |
| Predicate | hasCityCouncilWard |
P76280
|
FINISHED |
| Object | Cleveland Ward 9 |
—
|
NE NERFINISHED |
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: Cleveland Ward 9 | Statement: [Glenville, hasCityCouncilWard, Cleveland Ward 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCityCouncilWard Context triple: [Glenville, hasCityCouncilWard, Cleveland Ward 9]
-
A.
electoralWardFor
Indicates that one entity serves as the electoral ward or voting district in which another entity (such as a place or address) is located or represented.
-
B.
hasCouncilDistrict
Indicates that an entity is located within or represented by a specific council district.
-
C.
locatedInCityWard
chosen
Indicates that one entity is situated within the administrative boundaries of a specific city ward.
-
D.
hasWardAssembly
Indicates that a specified ward is associated with a particular assembly or representative governing body.
-
E.
districtCouncil
Indicates that an entity serves as, or is governed by, a district-level council within a larger administrative or political structure.
- 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_69ef53891af88190a193c5e2a1dac9b1 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 27, 2026, 1:42 p.m.