Triple
T17998227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transport Committee |
E430555
|
entity |
| Predicate | publicBodyStatus |
P26910
|
FINISHED |
| Object | committee of the legislature |
—
|
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: committee of the legislature | Statement: [Transport Committee, publicBodyStatus, committee of the legislature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicBodyStatus Context triple: [Transport Committee, publicBodyStatus, committee of the legislature]
-
A.
publicBody
Indicates that an entity functions as a governmental or publicly controlled organization that performs public duties or services.
-
B.
publicBodyType
chosen
Indicates the classification or category of a public body (such as its organizational or legal type) within a governmental or public-sector context.
-
C.
establishedBody
Indicates that an entity created, founded, or formally set up another entity, such as an organization, institution, or governing body.
-
D.
supportsBody
Indicates that one entity physically or structurally holds up, bears the weight of, or provides foundational stability for another entity’s body.
-
E.
bodyState
Indicates the physical condition or status that an entity’s body is currently in.
- 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_69d8b90364248190a37381adea932f42 |
completed | April 10, 2026, 8:46 a.m. |
| NER | Named-entity recognition | batch_69e4b3e6a2a881908af2d0a4a5053916 |
completed | April 19, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:23 a.m.