Triple
T6823480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buch der Lieder |
E156955
|
entity |
| Predicate | frequentlySetIn |
P64318
|
FINISHED |
| Object | Romantic Lieder tradition |
—
|
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: Romantic Lieder tradition | Statement: [Buch der Lieder, frequentlySetIn, Romantic Lieder tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frequentlySetIn Context triple: [Buch der Lieder, frequentlySetIn, Romantic Lieder tradition]
-
A.
isFrequently
Indicates that an action, state, or relationship occurs often or with high regularity between the related entities.
-
B.
frequentSettingType
chosen
Indicates that an entity commonly or regularly occurs, operates, or is used in a particular type of setting or environment.
-
C.
frequentlyAssignedIn
Indicates that something is regularly or repeatedly designated or allocated within a particular context, task, or setting.
-
D.
isFrequentlyIncludedIn
Indicates that something is regularly or commonly contained or made part of something else.
-
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_69c688298a288190af3f285d57f76bbe |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d580ca448190aa6d52908ca50e39 |
completed | March 27, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69c6d09bb4f881909bf20c188cb3e8e1 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:18 p.m.