Triple
T32518090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NomCom |
E831109
|
entity |
| Predicate | canBeStandingCommittee |
P196291
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [NomCom, canBeStandingCommittee, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeStandingCommittee Context triple: [NomCom, canBeStandingCommittee, true]
-
A.
isStandingCommittee
Indicates that an entity is a permanent committee with ongoing responsibilities, rather than a temporary or ad hoc group.
-
B.
isStandingCommitteeOf
Indicates that a committee is a permanent (standing) body formally established as part of, and operating under, a specific parent organization or legislative body.
-
C.
canBeChairOf
Indicates that an entity has the eligibility or capacity to serve as the chair (leader) of a specified group, committee, or organization.
-
D.
hasCommitteeType
Indicates that an entity is associated with a committee of a specified type or classification.
-
E.
hasCommittee
Indicates that an entity is associated with or overseen by a specific committee.
- 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_69f34923e1548190be0524205d8cdf8f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
| PDg | Predicate description generation | batch_69fe1fd58ad8819093d3d705e8521014 |
completed | May 8, 2026, 5:39 p.m. |
Created at: May 1, 2026, 1 a.m.