Triple
T247800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Subcommittee on Antitrust, Competition Policy and Consumer Rights |
E5076
|
entity |
| Predicate | committeeType |
P4423
|
FINISHED |
| Object | standing subcommittee |
—
|
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 subcommittee | Statement: [Subcommittee on Antitrust, Competition Policy and Consumer Rights, committeeType, standing subcommittee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: committeeType Context triple: [Subcommittee on Antitrust, Competition Policy and Consumer Rights, committeeType, standing subcommittee]
-
A.
hasCommitteeType
chosen
Indicates that an entity is associated with a committee of a specified type or classification.
-
B.
committeeMember
Indicates that an entity serves as a member of a particular committee.
-
C.
committeeFunction
Indicates that a committee performs, is responsible for, or is associated with a particular function or role.
-
D.
hasCommittee
Indicates that an entity is associated with or overseen by a specific committee.
-
E.
organizationType
Indicates the specific category or classification of an organization in terms of its nature, structure, or primary function.
- 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d154ebc819087a5c9dc4f62ff44 |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b64ea3081908de626a0e1445bdb |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.