Triple
T8927678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seattle City Council |
E212575
|
entity |
| Predicate | hasPublicMeetings |
P86237
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Seattle City Council, hasPublicMeetings, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicMeetings Context triple: [Seattle City Council, hasPublicMeetings, yes]
-
A.
allowsPublicHearings
Indicates that an entity permits public hearings to be held, allowing members of the public to attend and/or participate.
-
B.
heldPublicHearings
Indicates that formal meetings open to the public were conducted to gather input, discuss issues, or present information.
-
C.
hasPlenarySessions
Indicates that an event or organization includes formal plenary sessions as part of its activities or structure.
-
D.
hasGeneralAssembly
Indicates that an entity possesses or is associated with a general assembly as its formal deliberative or decision-making body.
-
E.
meetingsAre
Indicates that certain entities function as or are classified as meetings in relation to one another.
- 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_69ca8395c438819087d7cb844ab5990c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6672af10819084a6e50f0302f732 |
completed | April 1, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed3286c8190a21de2ee11f2639f |
completed | March 31, 2026, 11:54 p.m. |
| PDg | Predicate description generation | batch_69cc608331f88190bcb500ff63527f8a |
completed | April 1, 2026, 12:02 a.m. |
Created at: March 30, 2026, 6:57 p.m.