Triple
T36926058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boulder City Council Chambers |
E913344
|
entity |
| Predicate | typicalMeetingType |
P3082
|
FINISHED |
| Object | regular council meetings |
—
|
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: regular council meetings | Statement: [Boulder City Council Chambers, typicalMeetingType, regular council meetings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMeetingType Context triple: [Boulder City Council Chambers, typicalMeetingType, regular council meetings]
-
A.
meetingType
chosen
Indicates the specific category or format of a meeting that characterizes how it is organized or conducted.
-
B.
meetingsAre
Indicates that certain entities function as or are classified as meetings in relation to one another.
-
C.
meetingPeriod
Indicates the time span or duration during which a meeting takes place.
-
D.
typicalMeetingMonth
Indicates the month in which an entity most commonly or usually holds its meetings.
-
E.
typicalVisitType
Indicates the usual or most common category of visit associated with an 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_69f76e896c988190880c130e01303dd4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.