Triple
T11594821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tragic Overture, Op. 81 |
E274973
|
entity |
| Predicate | openingCharacter |
P100500
|
FINISHED |
| Object | forceful |
—
|
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: forceful | Statement: [Tragic Overture, Op. 81, openingCharacter, forceful]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingCharacter Context triple: [Tragic Overture, Op. 81, openingCharacter, forceful]
-
A.
openingRole
Indicates the functional role or position an entity holds at the initial or starting phase of an event, process, or sequence.
-
B.
openingElement
Indicates that one entity serves as the initial or starting element within a structured sequence, group, or construct in relation to another.
-
C.
openingOperator
Indicates that an entity initiates or performs the action of opening another entity or resource.
-
D.
openingLine
Indicates that one entity is the first line or initial statement that begins another entity, such as a text, speech, or conversation.
-
E.
openingTo
Indicates that one entity serves as an entrance, access point, or passage leading into or toward another entity.
- 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_69d6aae6b14c81908dc5a74bad7591f9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8946790d08190924d60bb4b523250 |
completed | April 10, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd20d188190863d1190d4c16048 |
completed | April 10, 2026, 2:17 a.m. |
| PDg | Predicate description generation | batch_69d87f2e67108190ac36bf47aac12fa8 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 8, 2026, 9:38 p.m.