Triple
T27979544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Nuttall |
E706580
|
entity |
| Predicate | servedAsMEPUntil |
P37781
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [Paul Nuttall, servedAsMEPUntil, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedAsMEPUntil Context triple: [Paul Nuttall, servedAsMEPUntil, 2019]
-
A.
servedAs
Indicates that one entity held and performed the role, position, or function associated with another entity for some period of time.
-
B.
servedAsFlagshipFrom
Indicates that an entity functioned as the primary or leading flagship of another entity starting from a specified point in time.
-
C.
operatedAsNameUntil
Indicates that an entity functioned or was known under a particular name up to a specified point in time.
-
D.
servedUntil
chosen
Indicates the ending time or date up to which an entity held a position, role, or service.
-
E.
servedInRole
Indicates that one entity performed duties or held a position within a specified role or office in relation to another entity.
- 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_69ef96b7f330819090f315318ba6977e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: April 27, 2026, 7:43 p.m.