Triple
T151697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 37th United Kingdom Parliament |
E3444
|
entity |
| Predicate | parliamentNumber |
P3122
|
FINISHED |
| Object | 37 |
—
|
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: 37 | Statement: [37th United Kingdom Parliament, parliamentNumber, 37]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parliamentNumber Context triple: [37th United Kingdom Parliament, parliamentNumber, 37]
-
A.
legislatureNumber
Indicates the specific numbered session or term of a legislative body associated with an entity or event.
-
B.
parliamentaryGroup
Indicates that an entity is a parliamentary group (or caucus) with which another political actor, such as a legislator or party, is affiliated or associated.
-
C.
legislativePeriod
Indicates the specific legislative term or session during which an action, event, or status is valid or took place.
-
D.
legislativeTermNumber
chosen
Indicates the ordinal number assigned to a specific legislative term within a sequence of legislative periods.
-
E.
electionNumber
Indicates the specific ordinal or identifying number assigned to a particular election within a series or system of elections.
- 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2580f55a88190b37b54ee0ed5ac7c |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a2565adaf48190b68ae4444ff83ccd |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.