Triple
T22985568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louth and Horncastle |
E571596
|
entity |
| Predicate | previousMPRepresentedUntil |
P4775
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [Louth and Horncastle, previousMPRepresentedUntil, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousMPRepresentedUntil Context triple: [Louth and Horncastle, previousMPRepresentedUntil, 2015]
-
A.
parliamentaryRepresentationEndYear
chosen
Indicates the calendar year in which an entity’s parliamentary representation or membership formally ended.
-
B.
previousMP
Indicates that one entity served as a Member of Parliament for a given constituency or position immediately before another specified entity.
-
C.
representedInParliamentSince
Indicates that an entity has held representation in a parliament continuously from a specified starting time.
-
D.
electorateUntil
Indicates that an entity serves as an electorate for another entity up to, but not beyond, a specified point in time.
-
E.
predecessorMPStartYear
Indicates that the subject entity’s predecessor began their term as a Member of Parliament in the specified year.
- 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_69e245b3c50481908bb3741ec9f40862 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182996ee08190ab74014ee7ecac2b |
completed | April 29, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69ef3b974e7c8190b8be11dbb4518693 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:49 p.m.