Triple
T8927679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seattle City Council |
E212575
|
entity |
| Predicate | openMeetingsLawApplies |
P11970
|
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, openMeetingsLawApplies, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openMeetingsLawApplies Context triple: [Seattle City Council, openMeetingsLawApplies, yes]
-
A.
openMeetingsRequirement
chosen
Indicates that certain meetings must be accessible to the public or non-participants, rather than being held in private or closed session.
-
B.
meetingsAre
Indicates that certain entities function as or are classified as meetings in relation to one another.
-
C.
tenantConference
Indicates a relationship where a tenant participates in, is associated with, or is the subject of a conference or meeting.
-
D.
convenesIn
Indicates that an entity brings together or assembles a group, meeting, or event at a specific place or venue.
-
E.
meetingType
Indicates the specific category or format of a meeting that characterizes how it is organized or conducted.
- 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_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. |
Created at: March 30, 2026, 6:57 p.m.