Triple
T37653989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UK Parliament 2005–2010 |
E937246
|
entity |
| Predicate | controllingPartyAtEnd |
P128856
|
FINISHED |
| Object | Labour Party (UK) |
—
|
NE NERFINISHED |
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: Labour Party (UK) | Statement: [UK Parliament 2005–2010, controllingPartyAtEnd, Labour Party (UK)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controllingPartyAtEnd Context triple: [UK Parliament 2005–2010, controllingPartyAtEnd, Labour Party (UK)]
-
A.
controlledByAtEnd
chosen
Indicates that one entity has control or governing authority over another entity at the final point or conclusion of a specified process, period, or event.
-
B.
resultingParty
Indicates the party that emerges as the outcome or beneficiary of a given event, process, or transaction.
-
C.
heldByEnd
Indicates that an object or item is being held or supported specifically at one of its ends by an agent or another object.
-
D.
surrenderingParty
Indicates the party that yields control, rights, or possession to another in a surrender or transfer arrangement.
-
E.
lastMPParty
Indicates the political party with which a member of parliament was most recently affiliated.
- 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_69f76ed4fe908190b8061c5c135e0971 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff48199b1c8190bb05872f8a4f4673 |
completed | May 9, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69ff4746b1cc8190854f70a124df7d04 |
completed | May 9, 2026, 2:40 p.m. |
Created at: May 3, 2026, 4:18 p.m.