Triple
T5455849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cadmus et Hermione |
E122474
|
entity |
| Predicate | hasBalletInterludes |
P46147
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Cadmus et Hermione, hasBalletInterludes, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBalletInterludes Context triple: [Cadmus et Hermione, hasBalletInterludes, true]
-
A.
balletInActs
Indicates that a ballet is structured or divided into a specified number of acts.
-
B.
hasBalletMaster
Indicates that an entity is associated with or overseen by a specific ballet master responsible for its ballet-related training, direction, or instruction.
-
C.
containsInterludes
chosen
Indicates that one entity (typically a work or composition) includes one or more interludes within its structure.
-
D.
hasDanceSequences
Indicates that the subject contains or features one or more dance sequences as part of its content or activity.
-
E.
balletInclusion
Indicates that ballet is included, featured, or incorporated as a component within something, such as a program, event, or curriculum.
- 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_69bd46424248819085282ddf50a565f3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd927c946c8190aef40679199fede3 |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a0d96c8190bd1299edbf764bbb |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:08 p.m.