Triple
T27990413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pearblossom Hwy., 11–18th April 1986, #2 |
E706853
|
entity |
| Predicate | creation dates referenced in title |
P184844
|
FINISHED |
| Object | 11–18 April 1986 |
—
|
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: 11–18 April 1986 | Statement: [Pearblossom Hwy., 11–18th April 1986, #2, creation dates referenced in title, 11–18 April 1986]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creation dates referenced in title Context triple: [Pearblossom Hwy., 11–18th April 1986, #2, creation dates referenced in title, 11–18 April 1986]
-
A.
titleDate
Indicates the date associated with a title, such as when it was granted, recorded, or became effective.
-
B.
yearTitleCreated
Indicates the year in which the referenced title (such as a work, document, or creative piece) was originally created.
-
C.
cataloguedDate
Indicates the date on which an item or entity was formally recorded or entered into a catalog or database.
-
D.
firstUseAsTitleDate
Indicates the date on which something was first used as a title.
-
E.
imageReleaseDate
Indicates the date on which an image was first made publicly available or officially released.
- 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_69ef96b8b8d88190bad5e4ae966bf14e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f7b628b17c8190aa058c1a51852a27 |
completed | May 3, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b5cadd308190a864245a21b08f9a |
completed | May 3, 2026, 8:53 p.m. |
Created at: April 27, 2026, 7:49 p.m.