Triple
T9430872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Bayadère |
E227370
|
entity |
| Predicate | scenographyStyle |
P88859
|
FINISHED |
| Object | exotic |
—
|
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: exotic | Statement: [La Bayadère, scenographyStyle, exotic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scenographyStyle Context triple: [La Bayadère, scenographyStyle, exotic]
-
A.
stageDesigner
Indicates that one entity is responsible for designing or creating the stage or set for a performance or event in relation to another entity.
-
B.
theatricalSetting
Indicates the spatial or contextual environment in which a theatrical performance or dramatic action takes place.
-
C.
stage
Indicates that an entity organizes, presents, or performs another entity (such as an event, show, or action) as a staged occurrence.
-
D.
theatreType
Indicates the specific category or kind of theatre associated with an entity, such as its format, style, or operational model.
-
E.
theatricalContext
Indicates the situational or environmental circumstances related to a theatrical performance or production in which an action or relationship occurs.
- F. None of above. chosen
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_69ca8436ba308190903e470776d2d893 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd7e5ed7408190beda5fb078e9345a |
completed | April 1, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69cca55548488190b171ae695a3212de |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89b3368819087a3d69270c1f185 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:49 p.m.