Triple
T14860485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hark! The Herald Angels Sing |
E349473
|
entity |
| Predicate | musicDate |
P115910
|
FINISHED |
| Object | 1840 |
—
|
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: 1840 | Statement: [Hark! The Herald Angels Sing, musicDate, 1840]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicDate Context triple: [Hark! The Herald Angels Sing, musicDate, 1840]
-
A.
playedOnDate
Indicates that an event or activity (such as a game, performance, or match) occurred on a specific calendar date.
-
B.
majorFestivalDate
Indicates the calendar date on which a major festival or significant celebratory event takes place.
-
C.
orchestrationDate
Indicates the date on which the orchestration (coordination or arrangement of related actions or processes) occurs or is scheduled to occur.
-
D.
eventDateAtLocation
Indicates that a specific event occurs on a particular date at a given location.
-
E.
dateOfEventCommand
Indicates a command or instruction that specifies or requests the date on which an event occurs.
- 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_69d822ed7e1881909b90fca143ad7e34 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded573cba881908d6d9ac570a64e5f |
completed | April 15, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69de8c1798c08190b433e9ad21e41a42 |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:54 a.m.