Triple
T28683701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seattle City Council District 3 |
E726071
|
entity |
| Predicate | positionInCityCouncil |
P192287
|
FINISHED |
| Object | one of seven geographic districts |
—
|
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: one of seven geographic districts | Statement: [Seattle City Council District 3, positionInCityCouncil, one of seven geographic districts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInCityCouncil Context triple: [Seattle City Council District 3, positionInCityCouncil, one of seven geographic districts]
-
A.
positionOnCouncils
Indicates that an entity holds a seat or role as a member on one or more councils.
-
B.
isRepresentedInCityCouncilBy
Indicates that a person or group has a designated representative who serves on the city council on their behalf.
-
C.
hasCouncilSeat
Indicates that an entity holds a position or seat on a governing council.
-
D.
roleInCouncil
Indicates that an entity holds a specific position or function within a council or governing body.
-
E.
hasCityCouncil
Indicates that an entity is governed or administered by a specific city council.
- 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_69f01d867608819086bc3e6b4f9de866 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
| PDg | Predicate description generation | batch_69fd05b965608190a3666410b9f8e125 |
completed | May 7, 2026, 9:35 p.m. |
Created at: April 28, 2026, 5:10 a.m.