Triple
T2031345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eleanor Rigby |
E44522
|
entity |
| Predicate | recordingEndDate |
P33169
|
FINISHED |
| Object | 1966-06-06 |
—
|
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: 1966-06-06 | Statement: [Eleanor Rigby, recordingEndDate, 1966-06-06]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordingEndDate Context triple: [Eleanor Rigby, recordingEndDate, 1966-06-06]
-
A.
recordingEnd
chosen
Indicates the point in time or event at which a recording process or recorded segment concludes.
-
B.
endDate
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
C.
firstRecordingDate
Indicates the date on which an entity’s first recording (e.g., audio, video, or similar captured performance) was made.
-
D.
deFactoEndDate
Indicates the date on which a relationship, status, or condition effectively ended in practice, regardless of any formal or official end date.
-
E.
endDateOfEntries
Indicates the date on which the referenced entries conclude or are no longer valid.
- 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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb915c9548190809d08c4d67466fb |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a656248190ac2ced196b35bc6b |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.