Triple
T19012740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lensky – tenor |
E465267
|
entity |
| Predicate | sceneHighlight |
P7326
|
FINISHED |
| Object | duel scene with Onegin in Act II |
—
|
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: duel scene with Onegin in Act II | Statement: [Lensky – tenor, sceneHighlight, duel scene with Onegin in Act II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sceneHighlight Context triple: [Lensky – tenor, sceneHighlight, duel scene with Onegin in Act II]
-
A.
sceneFeature
Indicates a characteristic, element, or attribute that is present within or helps define a particular scene.
-
B.
sceneLabel
Indicates the categorical label or type assigned to an entire scene based on its overall content or context.
-
C.
scenes
Indicates that one entity is a scene or setting in which the other entity occurs, appears, or is depicted.
-
D.
notableScene
chosen
Indicates that a particular scene is especially significant, memorable, or noteworthy within a work or context.
-
E.
focusFeature
Indicates that one entity is the primary or emphasized feature, aspect, or attribute being highlighted or concentrated on in relation to another.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6a9bac8819093f9af57000667b0 |
completed | April 20, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69e4a2fd80c081908237317a3a883e1c |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.