Triple
T37847178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vale of Clwyd (UK Parliament constituency) |
E943934
|
entity |
| Predicate | previousMPStart |
P70804
|
FINISHED |
| Object | 1997 |
—
|
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: 1997 | Statement: [Vale of Clwyd (UK Parliament constituency), previousMPStart, 1997]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousMPStart Context triple: [Vale of Clwyd (UK Parliament constituency), previousMPStart, 1997]
-
A.
previousMP
Indicates that one entity served as a Member of Parliament for a given constituency or position immediately before another specified entity.
-
B.
previousMPStartYear
chosen
Indicates the year in which the subject’s immediately preceding term as a Member of Parliament began.
-
C.
previousMPStatus
Indicates that an entity’s prior status or role as a Member of Parliament (MP) holds or held a particular condition or classification.
-
D.
previousMsp
Indicates that one entity was the immediately preceding managed service provider (MSP) for another entity in a sequence of such providers.
-
E.
earlierMPStartDate
Indicates that one entity’s MP start date occurs earlier in time than another entity’s MP start date.
- 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_69f76eed4d9c81908b1b71ba9e3b61fe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fff86e544c81908063f61b876c9d78 |
completed | May 10, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fff7e7cb688190977eeca41aad25b9 |
completed | May 10, 2026, 3:13 a.m. |
Created at: May 3, 2026, 4:19 p.m.