Triple
T20070252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Congleton (UK Parliament constituency) |
E499712
|
entity |
| Predicate | currentMPSince |
P19818
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Congleton (UK Parliament constituency), currentMPSince, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentMPSince Context triple: [Congleton (UK Parliament constituency), currentMPSince, 2010]
-
A.
currentMP
Indicates that the subject is the person who currently serves as a Member of Parliament representing the object’s constituency or jurisdiction.
-
B.
currentMSP
Indicates that an entity is the managed service provider (MSP) that is currently active or in effect for another entity.
-
C.
currentStatusSince
chosen
Indicates the point in time since which an entity has held its current status or state.
-
D.
lastMP
Indicates that one entity is the most recent Member of Parliament (MP) associated with, representing, or holding office for the other entity.
-
E.
mpcNumber
Indicates that an entity is associated with a specific MPC (Manufacturer Part Code or similar standardized catalog) identification number.
- 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6643798a4819081fa4e71c74b47bc |
completed | April 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:40 p.m.