Triple
T11819017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rocco |
E281075
|
entity |
| Predicate | premiereWorkDate |
P35994
|
FINISHED |
| Object | 1805 |
—
|
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: 1805 | Statement: [Rocco, premiereWorkDate, 1805]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: premiereWorkDate Context triple: [Rocco, premiereWorkDate, 1805]
-
A.
premiereWork
Indicates that a creative work is the first or debut piece presented or introduced by a particular creator or entity.
-
B.
workPremiereEvent
Indicates the event at which a creative work is first publicly presented or premiered.
-
C.
premiereCalendar
chosen
Indicates that an event, such as a show or performance, is scheduled to have its first public presentation on a specific date or within a particular calendar.
-
D.
associatedWorkDate
Indicates the date on which a related or associated work (such as a publication, performance, or creation) is linked to the subject entity.
-
E.
premiereStatus
Indicates the status or phase of an entity’s first public presentation or debut (such as whether it has premiered, is scheduled to premiere, or has not yet premiered).
- 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5e760988190b50d13bba5ef5b43 |
completed | April 10, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69d8a251fc08819095933f1d13c3b742 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.