Triple
T11631448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BWV2 (second edition) |
E276406
|
entity |
| Predicate | isRevision |
P35338
|
FINISHED |
| Object | expanded relative to the first edition |
—
|
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: expanded relative to the first edition | Statement: [BWV2 (second edition), isRevision, expanded relative to the first edition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRevision Context triple: [BWV2 (second edition), isRevision, expanded relative to the first edition]
-
A.
revisionOf
chosen
Indicates that one entity is a modified or updated version of another earlier entity.
-
B.
isAmendmentTo
Indicates that one item formally modifies, revises, or adds to the content or terms of another item.
-
C.
isTemporaryVersionOf
Indicates that one entity is a non-final, short-lived or provisional form of another, more permanent entity.
-
D.
revisionKnownAs
Indicates that a particular revision of an entity is referred to or identified by a specific alternative name or label.
-
E.
hasRevisionMechanism
Indicates that an entity is equipped with a mechanism or process for updating, modifying, or revising its content or state.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a25aa9188190ab13d79139f37e7e |
completed | April 10, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd94bdc819091fa2ed33eb31624 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.