Triple
T30304011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Les Sylphides |
E770728
|
entity |
| Predicate | firstStagedBy |
P143925
|
FINISHED |
| Object | Sergei Diaghilev |
E188396
|
NE 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: Sergei Diaghilev | Statement: [Les Sylphides, firstStagedBy, Sergei Diaghilev]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstStagedBy Context triple: [Les Sylphides, firstStagedBy, Sergei Diaghilev]
-
A.
stagedBy
Indicates that an event, performance, or production is organized, directed, or put on by a particular agent or entity.
-
B.
firstStagedIn
Indicates the place, venue, or context where a performance, play, or production was originally staged for the first time.
-
C.
isStagedBy
Indicates that something (such as a performance, event, or production) is organized, directed, or put on by a particular agent or entity.
-
D.
firstSummitedBy
Indicates that a particular mountain or peak was first successfully climbed to its summit by a specified person or group.
-
E.
firstStagingDirector
chosen
Indicates that the subject served as the original staging director responsible for the first production or staging of the work or event.
- F. None of above.
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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a01c41dfe248190a68f4a262591b30f |
completed | May 11, 2026, 11:57 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a27989d5fd0819097aab24fa5d9ce33 |
completed | June 9, 2026, 4:37 a.m. |
| PD | Predicate disambiguation | batch_6a01c375d14c8190a15bfa12623588a9 |
completed | May 11, 2026, 11:54 a.m. |
Created at: April 29, 2026, 7:49 p.m.