Triple
T31806651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vexations |
E811889
|
entity |
| Predicate | anticipatedMovement |
P167061
|
FINISHED |
| Object | conceptual music |
—
|
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: conceptual music | Statement: [Vexations, anticipatedMovement, conceptual music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: anticipatedMovement Context triple: [Vexations, anticipatedMovement, conceptual music]
-
A.
coveredMovement
Indicates that one entity moves while being physically shielded, concealed, or protected by another entity or environmental feature.
-
B.
movementIn
Indicates a relationship where an entity moves within, into, or inside a specified area, space, or container.
-
C.
intendedDisplacement
chosen
Indicates that an action or event is meant to cause a change in position or location of an entity, regardless of whether that movement actually occurs.
-
D.
movedFor
Indicates that one entity changed its location or position for the benefit, purpose, or in response to another entity.
-
E.
cessionLocation
Indicates the place where a transfer or ceding of rights, territory, or control occurs.
- 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:43 p.m.