Triple
T8813936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Impromptus, D. 899 |
E209730
|
entity |
| Predicate | hasOpusGrouping |
P74342
|
FINISHED |
| Object | group of four impromptus |
—
|
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: group of four impromptus | Statement: [Impromptus, D. 899, hasOpusGrouping, group of four impromptus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpusGrouping Context triple: [Impromptus, D. 899, hasOpusGrouping, group of four impromptus]
-
A.
ISOGroupingStatus
Indicates the relationship between an entity and its classification or status within an ISO-defined grouping or category.
-
B.
hasCoveringGroup
Indicates that one group serves as a covering group (typically a covering or universal covering in the group-theoretic sense) for another group.
-
C.
hasStationGroup
Indicates that an entity is associated with, or belongs to, a particular group or collection of stations.
-
D.
groupedInto
chosen
Indicates that multiple entities are collected or organized together as members of a common group or category.
-
E.
hasSubfieldGroup
Indicates that an entity includes or is associated with a specific subgroup of related subfields within its overall structure or domain.
- 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5ff1a4448190b5559f440d264442 |
completed | March 31, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1f28ec8190a34311cb412920c2 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:45 p.m.