Triple
T32902773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senta’s Ballad |
E841654
|
entity |
| Predicate | settingWithinOpera |
P174350
|
FINISHED |
| Object | a Norwegian coastal village |
—
|
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: a Norwegian coastal village | Statement: [Senta’s Ballad, settingWithinOpera, a Norwegian coastal village]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingWithinOpera Context triple: [Senta’s Ballad, settingWithinOpera, a Norwegian coastal village]
-
A.
placeInOpera
chosen
Indicates that one entity is a location or setting where an opera takes place or is staged.
-
B.
fromOperaSetIn
Indicates that an opera originates from or is part of a narrative that is set in a particular place or setting.
-
C.
appearsInOperaBy
Indicates that one entity (typically a character, role, or element) is featured or takes part in an opera created or composed by another entity.
-
D.
operaAct
Indicates that an entity performs in or takes part in an act (segment) of an opera performance.
-
E.
operaEnÁmbito
Indicates that an entity operates, functions, or carries out its activities within a specified domain, field, or scope.
- 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_69f34946a5208190bbd79f0fec4323bd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 1, 2026, 1:19 a.m.