Triple
T12935847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Lothian (UK Parliament constituency) |
E309505
|
entity |
| Predicate | previousNameEndYear |
P17450
|
FINISHED |
| Object | 2005 |
—
|
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: 2005 | Statement: [East Lothian (UK Parliament constituency), previousNameEndYear, 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousNameEndYear Context triple: [East Lothian (UK Parliament constituency), previousNameEndYear, 2005]
-
A.
previousNamePeriod
Indicates the time span during which an entity was known by a former name before changing to its current name.
-
B.
previousNameUsedUntil
Indicates that a particular name was used for an entity up to (but not necessarily including) a specified end date or time.
-
C.
formerNamePeriodEnd
chosen
Indicates the point in time when an entity stopped using a former name.
-
D.
formerNamePeriodStart
Indicates the date or time point when an entity began using a former name that is being recorded.
-
E.
originalNameUsedInYears
Indicates that a particular original name was in use for an entity during a specified range of years.
- 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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97db69f548190a1a693bc0d6c191a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 5:42 p.m.