Triple
T7839144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir David Amess |
E181759
|
entity |
| Predicate | startTimeAsMPForBasildon |
P19506
|
FINISHED |
| Object | 1983-06-09 |
—
|
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: 1983-06-09 | Statement: [Sir David Amess, startTimeAsMPForBasildon, 1983-06-09]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeAsMPForBasildon Context triple: [Sir David Amess, startTimeAsMPForBasildon, 1983-06-09]
-
A.
startTime (MP for Bedwellty)
Indicates the time at which the event or activity associated with MP for Bedwellty begins.
-
B.
startTimeAsRepresentative
chosen
Indicates the time at which an entity begins serving or acting in a representative capacity.
-
C.
startTimeAsCardinal
Indicates the specific clock time at which an event or action begins, expressed as a cardinal (numeric) value rather than a textual or formatted time.
-
D.
startTime_ma
Indicates the time at which an event, action, or relationship begins, measured in millions of years ago (Ma).
-
E.
endTime (MP for Bedwellty)
Indicates the time at which the specified event, activity, or state associated with MP for Bedwellty concludes.
- 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_69ca8284a25c8190a1a20afad30da792 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb14c4680481908628d22bbe4842f4 |
completed | March 31, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_69cae91e98988190abd4ece75932c589 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:47 p.m.