Triple
T32897945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euryanthe |
E841526
|
entity |
| Predicate | overturePopularity |
P42306
|
FINISHED |
| Object | standard concert repertoire |
—
|
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: standard concert repertoire | Statement: [Euryanthe, overturePopularity, standard concert repertoire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overturePopularity Context triple: [Euryanthe, overturePopularity, standard concert repertoire]
-
A.
peakPopularity
Indicates the time or context in which something reaches its highest level of popularity relative to other times or contexts.
-
B.
soundtrackPopularity
Indicates how widely liked, acclaimed, or frequently consumed a soundtrack is relative to others.
-
C.
popularityContext
chosen
Indicates the situational or domain-specific setting in which something’s popularity or level of public favor is evaluated.
-
D.
popularity
Indicates how widely liked, admired, or favored something or someone is by a group of people.
-
E.
internationalPopularity
Indicates that something is widely recognized, appreciated, or favored across multiple countries or cultures.
- 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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:19 a.m.