Triple
T11205707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prime Minister's Policy Unit |
E265153
|
entity |
| Predicate | isLegislativeBody |
P97852
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Prime Minister's Policy Unit, isLegislativeBody, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLegislativeBody Context triple: [Prime Minister's Policy Unit, isLegislativeBody, false]
-
A.
legislativeBodyOf
Indicates that one entity is the official legislative body (lawmaking assembly) of another entity, typically a political unit such as a country, state, or city.
-
B.
hasLegislativeType
Indicates that something is associated with, classified by, or characterized as a particular type or category of legislation or legislative measure.
-
C.
isElectedBody
Indicates that an entity is a formal decision-making group whose members attain their positions through an election process.
-
D.
hasLegislatureType
Indicates the specific form or system of legislature that an entity possesses or operates under.
-
E.
legislativeBodyMemberOf
Indicates that an individual serves as a member of a specified legislative body or assembly.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8d4eef88190a7f05bca82d919b9 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf83464819087529d47d025d313 |
completed | April 9, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69d77062271c8190b63da714ab5beff9 |
completed | April 9, 2026, 9:24 a.m. |
Created at: April 8, 2026, 9:30 p.m.