Triple
T17997670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Defence Committee |
E430543
|
entity |
| Predicate | isNonPartisanBody |
P5069
|
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: [Defence Committee, isNonPartisanBody, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNonPartisanBody Context triple: [Defence Committee, isNonPartisanBody, true]
-
A.
isNonpartisanOffice
chosen
Indicates that the office or position is not affiliated with, controlled by, or contested along formal political party lines.
-
B.
isLegislativeBody
Indicates that the subject entity functions as an official law-making or legislative body within a political or organizational system.
-
C.
isElectedBody
Indicates that an entity is a formal decision-making group whose members attain their positions through an election process.
-
D.
isNonPoliticalOffice
Indicates that the office or position in question is not associated with political power, political decision-making, or elected political roles.
-
E.
isPartOfGovernment
Indicates that an entity belongs to, is included within, or functions as a component of a governmental body or system.
- 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_69e4b3e5c63c8190890436366c4a47c5 |
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.