Triple
T25069807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beethoven’s Egmont Overture |
E627876
|
entity |
| Predicate | widelyPerformed |
P139549
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Beethoven’s Egmont Overture, widelyPerformed, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: widelyPerformed Context triple: [Beethoven’s Egmont Overture, widelyPerformed, yes]
-
A.
isWidelyPerformed
chosen
Indicates that an action or behavior is carried out by a large number of individuals or groups across many contexts or locations.
-
B.
frequentPerformance
Indicates that an entity regularly or repeatedly carries out a particular performance or activity over a period of time.
-
C.
isFrequentlyPerformedBy
Indicates that an action or activity is carried out often or on a regular basis by a particular entity.
-
D.
performedTo
Indicates that an action or performance is directed toward or carried out on a particular entity.
-
E.
isFrequentlyPerformedOnTourBy
Indicates that an action or piece (such as a song, routine, or performance) is regularly and commonly carried out by an entity while they are on tour.
- 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f45d13c684819085690724d772616e |
completed | May 1, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:10 a.m.