Triple
T32209066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La voix |
E822749
|
entity |
| Predicate | hasStagePerformanceElements |
P79011
|
FINISHED |
| Object | classical crossover staging |
—
|
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: classical crossover staging | Statement: [La voix, hasStagePerformanceElements, classical crossover staging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStagePerformanceElements Context triple: [La voix, hasStagePerformanceElements, classical crossover staging]
-
A.
hasPerformanceElement
chosen
Indicates that one entity includes, contains, or is associated with a specific performance-related component or element.
-
B.
hasStageAppearanceWith
Indicates that two or more entities appear together in the same staged performance or event.
-
C.
hasLivePerformanceComponent
Indicates that something includes or involves a live performance as a significant component or feature.
-
D.
hasStageAppearance
Indicates that an entity makes or has made a performance or appearance on a stage, typically before an audience.
-
E.
hasLivePerformanceStyle
Indicates that an entity is associated with a particular style or manner of live performance.
- 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fef3ceef648190b58027c93d757438 |
completed | May 9, 2026, 8:43 a.m. |
| PD | Predicate disambiguation | batch_69fef359da2c819091a034387b08821f |
completed | May 9, 2026, 8:42 a.m. |
Created at: May 1, 2026, 12:37 a.m.