Triple
T22383524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beethoven’s letters |
E553333
|
entity |
| Predicate | hasPublishedEditions |
P147450
|
FINISHED |
| Object | critical scholarly editions |
—
|
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: critical scholarly editions | Statement: [Beethoven’s letters, hasPublishedEditions, critical scholarly editions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublishedEditions Context triple: [Beethoven’s letters, hasPublishedEditions, critical scholarly editions]
-
A.
hasSerializedEditions
Indicates that an entity has one or more serialized editions or installments derived from it.
-
B.
hasEditionIn
Indicates that one entity has a specific edition or version that exists or is available in another entity (such as a particular format, language, or location).
-
C.
numberOfEditions
Indicates the total count of distinct editions associated with a given entity.
-
D.
hasPublication
Indicates that an entity is associated with or responsible for a specific publication.
-
E.
hasCollectedEdition
Indicates that one entity possesses or maintains a special or curated edition or version of another entity as part of a collection.
- 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_69e11e4cf87c8190a1ff474daec326b7 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1582d8e548190a7330de49d519675 |
completed | April 29, 2026, 1 a.m. |
| PD | Predicate disambiguation | batch_69e73015484c8190a9a0b9f554b61a81 |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e73597b51c8190aeff27f4779b82f3 |
completed | April 21, 2026, 8:30 a.m. |
Created at: April 16, 2026, 8:45 p.m.