Triple
T24317940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bach English Suites |
E612872
|
entity |
| Predicate | likelyCompositionLocation |
P39025
|
FINISHED |
| Object | Weimar |
—
|
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: Weimar | Statement: [Bach English Suites, likelyCompositionLocation, Weimar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyCompositionLocation Context triple: [Bach English Suites, likelyCompositionLocation, Weimar]
-
A.
likelyComposition
Indicates that one entity is probably a component or constituent part of another entity, though this compositional relationship is uncertain or inferred rather than definite.
-
B.
possiblePlaceOfComposition
chosen
Indicates that a location is a plausible or hypothesized place where a work was composed.
-
C.
possibleLocation
Indicates that an entity may be located at, or could plausibly occur in, a specified place or spatial context.
-
D.
likelyLocatedIn
Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
-
E.
placeOfComposition
Indicates the location where a work was created or composed.
- 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_69e2d7da491c8190b6e6218af50923db |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292a916c8819096d018e7ffaf483b |
completed | April 29, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f1c45f45888190a9ccc225906c34bd |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 1:47 a.m.