Triple
T16399531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Profil Edition Günter Hänssler |
E398273
|
entity |
| Predicate | catalogueIncludes |
P123276
|
FINISHED |
| Object | 20th-century repertoire |
—
|
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: 20th-century repertoire | Statement: [Profil Edition Günter Hänssler, catalogueIncludes, 20th-century repertoire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catalogueIncludes Context triple: [Profil Edition Günter Hänssler, catalogueIncludes, 20th-century repertoire]
-
A.
catalogueFor
Indicates that one entity serves as a catalog or organized listing that describes, indexes, or inventories another entity.
-
B.
catalogueAccess
Indicates that an entity has permission to view or interact with a specified catalogue or collection of items.
-
C.
productIncludes
Indicates that a product contains, comprises, or is composed of the specified component, item, or feature.
-
D.
catalogueType
Indicates the classification or category assigned to an item within a catalogue or cataloging system.
-
E.
catalogueSystem
Indicates a relationship where one entity serves as or belongs to a cataloging system that organizes, indexes, or classifies other entities.
- 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e327cdc62481909de144b09a921e63 |
completed | April 18, 2026, 6:42 a.m. |
| PD | Predicate disambiguation | batch_69e226fe1dd08190865c181721f8c348 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:09 a.m.