Triple
T37610975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beethoven’s Tenth |
E935782
|
entity |
| Predicate | impliesInfluenceOf |
P189076
|
FINISHED |
| Object | Beethoven’s symphonic style |
—
|
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: Beethoven’s symphonic style | Statement: [Beethoven’s Tenth, impliesInfluenceOf, Beethoven’s symphonic style]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impliesInfluenceOf Context triple: [Beethoven’s Tenth, impliesInfluenceOf, Beethoven’s symphonic style]
-
A.
influenceOf
Indicates that one entity affects, shapes, or alters the state, behavior, or properties of another entity.
-
B.
influencedIn
Indicates that one entity had an effect on or shaped another entity within a specific context, domain, or setting.
-
C.
hasImplicationsFor
Indicates that one entity’s state, action, or condition leads to consequences, effects, or relevance for another entity.
-
D.
incorporatesInfluence
Indicates that one entity integrates or absorbs the influence, ideas, or characteristics of another into itself.
-
E.
consequenceOfInfluence
Indicates that one event, state, or condition occurs as a result of the influence or impact exerted by another.
- 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbb083ab708190a18b045311106f27 |
completed | May 6, 2026, 9:20 p.m. |
Created at: May 3, 2026, 4:18 p.m.