Triple
T2361674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston City Council |
E47286
|
entity |
| Predicate | hasCommitteeStructure |
P14616
|
FINISHED |
| Object | standing committees |
—
|
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: standing committees | Statement: [Boston City Council, hasCommitteeStructure, standing committees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommitteeStructure Context triple: [Boston City Council, hasCommitteeStructure, standing committees]
-
A.
hasCommittee
Indicates that an entity is associated with or overseen by a specific committee.
-
B.
hasCommitteeFunction
Indicates that a committee is assigned or performs a specific function, role, or responsibility.
-
C.
hasStandingCommittees
chosen
Indicates that an entity maintains one or more permanent (standing) committees as part of its organizational structure.
-
D.
hasCommitteeType
Indicates that an entity is associated with a committee of a specified type or classification.
-
E.
hasTechnicalCommittee
Indicates that an entity is associated with or overseen by a specific technical committee.
- 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_69a88a1a4a6081908645b0f2914521ab |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc723c66481908a9b94991f651b3b |
completed | March 7, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69abc599b92c819093d9e15d4437705d |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:55 p.m.