Triple
T17955482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beethoven’s ten violin sonatas |
E448933
|
entity |
| Predicate | frequentIn |
P46711
|
FINISHED |
| Object | conservatory curricula |
—
|
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: conservatory curricula | Statement: [Beethoven’s ten violin sonatas, frequentIn, conservatory curricula]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frequentIn Context triple: [Beethoven’s ten violin sonatas, frequentIn, conservatory curricula]
-
A.
isFrequentlyIncludedIn
chosen
Indicates that something is regularly or commonly contained or made part of something else.
-
B.
isFrequently
Indicates that an action, state, or relationship occurs often or with high regularity between the related entities.
-
C.
frequentlyAssignedIn
Indicates that something is regularly or repeatedly designated or allocated within a particular context, task, or setting.
-
D.
isFrequentlyPerformedBy
Indicates that an action or activity is carried out often or on a regular basis by a particular entity.
-
E.
frequentOccasion
Indicates that a particular event, situation, or condition occurs repeatedly or commonly over time.
- 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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4afafe814819085300163f73de5f2 |
completed | April 19, 2026, 10:34 a.m. |
| PD | Predicate disambiguation | batch_69e3f8f2bd088190b1e22ad4d9cc8b13 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:21 a.m.