Triple
T19967197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Yeletsky |
E479967
|
entity |
| Predicate | firstPerformanceOfWorkAppearingIn |
P49581
|
FINISHED |
| Object | 1890 |
—
|
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: 1890 | Statement: [Prince Yeletsky, firstPerformanceOfWorkAppearingIn, 1890]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPerformanceOfWorkAppearingIn Context triple: [Prince Yeletsky, firstPerformanceOfWorkAppearingIn, 1890]
-
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.
firstPerformanceWork
Indicates that a performance is the debut or initial presentation of a particular work.
-
C.
firstPerformance
Indicates that an entity marks the initial or debut performance of another entity, such as a work, artist, or production.
-
D.
firstPerformancePlaceOfWork
Indicates the place of work where an entity had its first performance or debut.
-
E.
firstPerformanceProduction
Indicates that a production is the one in which a work (e.g., a play, musical, or performance piece) was first publicly performed.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65bc5e41881908c1e8867820f1c0c |
completed | April 20, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69e537f7e4848190b431a69ec3f1b609 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.