Triple
T31434020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MWV A 14 |
E801873
|
entity |
| Predicate | catalogueSystemCreator |
P173773
|
FINISHED |
| Object | Mendelssohn-Werkverzeichnis editors |
—
|
NE NERFINISHED |
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: Mendelssohn-Werkverzeichnis editors | Statement: [MWV A 14, catalogueSystemCreator, Mendelssohn-Werkverzeichnis editors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catalogueSystemCreator Context triple: [MWV A 14, catalogueSystemCreator, Mendelssohn-Werkverzeichnis editors]
-
A.
catalogueSystem
Indicates a relationship where one entity serves as or belongs to a cataloging system that organizes, indexes, or classifies other entities.
-
B.
catalogueFor
Indicates that one entity serves as a catalog or organized listing that describes, indexes, or inventories another entity.
-
C.
catalogueType
Indicates the classification or category assigned to an item within a catalogue or cataloging system.
-
D.
catalogueScheme
Indicates the classification or organizational system under which items are catalogued or arranged.
-
E.
mainCreator
Indicates that an entity is the primary or most responsible creator of another entity (such as a work, product, or artifact).
- 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ba1733408190af579d93a7946508 |
completed | May 3, 2026, 2:59 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: April 30, 2026, 9 p.m.