Triple
T9041546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hammersmith Odeon London ’75 |
E216641
|
entity |
| Predicate | recordedOnDate |
P86046
|
FINISHED |
| Object | 1975-11-18 |
—
|
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: 1975-11-18 | Statement: [Hammersmith Odeon London ’75, recordedOnDate, 1975-11-18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordedOnDate Context triple: [Hammersmith Odeon London ’75, recordedOnDate, 1975-11-18]
-
A.
recordedBetween
Indicates that an event or data item was recorded at a time that falls within a specified start and end time interval.
-
B.
reRecordedVersionReleaseDate
Indicates the date on which a re-recorded version of an existing work is officially released.
-
C.
firstRecordingDate
Indicates the date on which an entity’s first recording (e.g., audio, video, or similar captured performance) was made.
-
D.
cataloguedDate
Indicates the date on which an item or entity was formally recorded or entered into a catalog or database.
-
E.
recordedFor
Indicates that something has been documented, captured, or logged on behalf of or in association with a particular entity or context.
- 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_69ca83d22d488190adbce5e020e9cd1d |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6b110fcc8190a09e8ac5d98e399e |
completed | April 1, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee566b081909e3cdaf551dbd0ec |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f4f1cb48190a025d1b3d8d7a790 |
completed | March 31, 2026, 11:57 p.m. |
Created at: March 30, 2026, 7:09 p.m.