Triple
T15118676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weaver Vale |
E361107
|
entity |
| Predicate | predecessorMPStartYear |
P117396
|
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: [Weaver Vale, predecessorMPStartYear, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorMPStartYear Context triple: [Weaver Vale, predecessorMPStartYear, 2010]
-
A.
formerMPStartYear
Indicates the year in which an individual began their period of service as a former Member of Parliament (i.e., the start year of their tenure as an MP).
-
B.
previousMPStartYear
Indicates the year in which the subject’s immediately preceding term as a Member of Parliament began.
-
C.
representedInParliamentSince
Indicates that an entity has held representation in a parliament continuously from a specified starting time.
-
D.
hasFormerMP
Indicates that an entity previously served as a Member of Parliament for another entity (such as a constituency, party, or legislative body), but no longer holds that position.
-
E.
predecessorAsPrimeMinister
Indicates that one person previously held the office of Prime Minister immediately before another person.
- F. None of above. chosen
Provenance (4 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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0059e036c8190959ff3bde8f2356f |
completed | April 15, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69deb96c1d9c81909351558ed97bc5b7 |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec71e8dcc81908badc834b6ccf273 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:06 a.m.