Triple
T31394851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoboken-like Mendelssohn-Werkverzeichnis (MWV N 15) |
E800836
|
entity |
| Predicate | catalogSection |
P81111
|
FINISHED |
| Object | N |
—
|
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: N | Statement: [Hoboken-like Mendelssohn-Werkverzeichnis (MWV N 15), catalogSection, N]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catalogSection Context triple: [Hoboken-like Mendelssohn-Werkverzeichnis (MWV N 15), catalogSection, N]
-
A.
collectionSection
chosen
Indicates a relationship where a collection is divided into or associated with a specific section or subdivision within it.
-
B.
catalogCategory
Indicates that an item or entity is assigned to, or belongs within, a specific catalog category.
-
C.
catalog
Indicates the action of systematically listing, organizing, or recording items or information into a structured collection or database.
-
D.
shopSection
Indicates the specific section or area within a shop where an item, activity, or service is located or takes place.
-
E.
catalogPartOf
Indicates that one catalog item is a component, section, or subset of a larger catalog or cataloged collection.
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 29, 2026, 9:19 p.m.