Triple
T8900891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riders to the Sea |
E211926
|
entity |
| Predicate | firstProfessionalPerformanceDate |
P21118
|
FINISHED |
| Object | 1953-01-17 |
—
|
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: 1953-01-17 | Statement: [Riders to the Sea, firstProfessionalPerformanceDate, 1953-01-17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstProfessionalPerformanceDate Context triple: [Riders to the Sea, firstProfessionalPerformanceDate, 1953-01-17]
-
A.
firstPerformanceAt
Indicates the location or event at which an entity (such as a work or performance) was first performed.
-
B.
dateOfFirstPerformance
chosen
Indicates the date on which a work, such as a play or musical composition, was first publicly performed.
-
C.
firstUSPerformanceDate
Indicates the date on which something was first performed in the United States.
-
D.
firstPerformanceBy
Indicates that the referenced performance is the earliest or debut performance carried out by the specified entity.
-
E.
firstPerformance
Indicates that an entity marks the initial or debut performance of another entity, such as a work, artist, or production.
- 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_69ca83918d3081909b326fa3750cb8c8 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6428ffc48190814f6b865961dbd1 |
completed | April 1, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2bfb38819083d5eb1af8ccf4d6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:54 p.m.