Triple
T25069809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beethoven’s Egmont Overture |
E627876
|
entity |
| Predicate | oftenRecorded |
P157929
|
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, oftenRecorded, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenRecorded Context triple: [Beethoven’s Egmont Overture, oftenRecorded, yes]
-
A.
oftenRecordedIn
Indicates that instances of one entity are frequently documented, logged, or captured within another entity (such as a medium, dataset, or record).
-
B.
recorded
Indicates that one entity captured, stored, or documented information, audio, video, or data about another entity or event.
-
C.
laterRecordedIn
Indicates that the referenced information or event was documented or captured at a later time in the specified source or record.
-
D.
mainlyRecordedDuring
Indicates that an event, activity, or phenomenon was predominantly documented or captured within a specific time period or context.
-
E.
recordedFor
Indicates that something has been documented, captured, or logged on behalf of or in association with a particular entity or context.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 18, 2026, 6:10 a.m.