Triple
T34792647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dandini |
E1002987
|
entity |
| Predicate | firstPerformanceOfWorkAppearsIn |
P49581
|
FINISHED |
| Object | 1817 |
—
|
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: 1817 | Statement: [Dandini, firstPerformanceOfWorkAppearsIn, 1817]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPerformanceOfWorkAppearsIn Context triple: [Dandini, firstPerformanceOfWorkAppearsIn, 1817]
-
A.
firstPerformanceOfWorkAppearedIn
chosen
Indicates that a given performance is the earliest known or documented performance in which a particular work was presented or appeared.
-
B.
firstPerformanceLocationOfWorkAppearingIn
Indicates the location where a work was first performed or premiered.
-
C.
firstPerformanceWork
Indicates that a performance is the debut or initial presentation of a particular work.
-
D.
firstPerformanceOfSourceWork
Indicates that the referenced performance is the earliest known or original performance of the specified source work.
-
E.
firstPerformancePlaceOfWork
Indicates the place of work where an entity had its first performance or debut.
- 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_69f76db47d408190a24fc7164439ea2d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 3:59 p.m.