Triple
T32518091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NomCom |
E831109
|
entity |
| Predicate | canBeAdHocCommittee |
P196332
|
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, canBeAdHocCommittee, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeAdHocCommittee Context triple: [NomCom, canBeAdHocCommittee, true]
-
A.
canBeStandingCommittee
Indicates that an entity has the authority or eligibility to function as a standing committee within a given organizational or legislative structure.
-
B.
hasCommittee
Indicates that an entity is associated with or overseen by a specific committee.
-
C.
hasCommitteeType
Indicates that an entity is associated with a committee of a specified type or classification.
-
D.
isStandingCommittee
Indicates that an entity is a permanent committee with ongoing responsibilities, rather than a temporary or ad hoc group.
-
E.
hasCommitteeFunction
Indicates that a committee is assigned or performs a specific function, role, or responsibility.
- 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_69fe21b0cba48190b56c39e9f1c0eafa |
completed | May 8, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69fe204576848190aecf204e2adba5dc |
completed | May 8, 2026, 5:41 p.m. |
| PDg | Predicate description generation | batch_69fe21afdc4c8190913ac4b55a9a5f52 |
completed | May 8, 2026, 5:47 p.m. |
Created at: May 1, 2026, 1 a.m.