Triple
T17394566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seattle City Council District 2 |
E422916
|
entity |
| Predicate | positionCount |
P1029
|
FINISHED |
| Object | 1 council seat |
—
|
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 council seat | Statement: [Seattle City Council District 2, positionCount, 1 council seat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionCount Context triple: [Seattle City Council District 2, positionCount, 1 council seat]
-
A.
positionNumber
Indicates the specific ordinal or identifying number assigned to a position within an ordered set or organizational structure.
-
B.
numberOfPositions
chosen
Indicates the total count of distinct positions or roles associated with a given entity.
-
C.
numberOfCounts
Indicates the total quantity or tally of discrete occurrences, items, or instances associated with an entity or event.
-
D.
movementCount
Indicates the number of times a movement or relocation action has occurred between the related entities.
-
E.
count
Indicates the numerical quantity or total number of instances of a specified entity or event.
- 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43abbd84881908af91bb7c9784026 |
completed | April 19, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.