Triple
T31806657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vexations |
E811889
|
entity |
| Predicate | firstCompletePerformanceOrganizer |
P21090
|
FINISHED |
| Object | John Cage |
E119363
|
NE 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: John Cage | Statement: [Vexations, firstCompletePerformanceOrganizer, John Cage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstCompletePerformanceOrganizer Context triple: [Vexations, firstCompletePerformanceOrganizer, John Cage]
-
A.
firstCompletePerformanceConductor
Indicates the conductor who led the first complete performance of a given work.
-
B.
firstCompletePerformancePlace
Indicates the location where something (such as a work, event, or performance) was first fully performed or completed in its entirety.
-
C.
firstOrganizer
chosen
Indicates that an entity serves as the primary or initial organizer in relation to another event, group, or activity.
-
D.
finalPerformer
Indicates that an entity is the last or concluding performer in a sequence of performances or performers.
-
E.
firstPerformanceCompany
Indicates the company that first performed or premiered a given work or production.
- F. None of above.
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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2e6598b548819096b458f43813fa9c |
completed | June 14, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 11:43 p.m.