Triple
T31394846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoboken-like Mendelssohn-Werkverzeichnis (MWV N 15) |
E800836
|
entity |
| Predicate | describesKey |
P1150
|
FINISHED |
| Object | D minor |
—
|
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: D minor | Statement: [Hoboken-like Mendelssohn-Werkverzeichnis (MWV N 15), describesKey, D minor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesKey Context triple: [Hoboken-like Mendelssohn-Werkverzeichnis (MWV N 15), describesKey, D minor]
-
A.
describedIn
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
-
B.
keyEventDescribed
Indicates that a key or significant event is explicitly described or detailed in relation to an entity or context.
-
C.
describes
Indicates that one entity provides an explanation, representation, or account of another entity or concept.
-
D.
typicalKey
chosen
Indicates that the referenced key is the standard or most commonly used key associated with an entity or context.
-
E.
describedThrough
Indicates that something is explained, represented, or conveyed by means of a particular medium, method, or description.
- 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_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 29, 2026, 9:19 p.m.