Triple
T25720196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 22nd Parliament of the United Kingdom |
E644969
|
entity |
| Predicate | hasLegislativeTermNumber |
P3122
|
FINISHED |
| Object | 22 |
—
|
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: 22 | Statement: [22nd Parliament of the United Kingdom, hasLegislativeTermNumber, 22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegislativeTermNumber Context triple: [22nd Parliament of the United Kingdom, hasLegislativeTermNumber, 22]
-
A.
legislativeTermNumber
chosen
Indicates the ordinal number assigned to a specific legislative term within a sequence of legislative periods.
-
B.
legislativePeriod
Indicates the specific legislative term or session during which an action, event, or status is valid or took place.
-
C.
hasGovernmentNumberInTerm
Indicates that a government-assigned identification number is associated with or valid during a specific term or period.
-
D.
legislativeTermType
Indicates the specific category or classification of a legislative term within a legislative body or system.
-
E.
legislatureNumber
Indicates the specific numbered session or term of a legislative body associated with an entity or event.
- 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 21, 2026, 9:56 p.m.