Triple
T29325519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ballet for Martha |
E743630
|
entity |
| Predicate | laterOrchestratedAs |
P196622
|
FINISHED |
| Object | orchestral suite |
—
|
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: orchestral suite | Statement: [Ballet for Martha, laterOrchestratedAs, orchestral suite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterOrchestratedAs Context triple: [Ballet for Martha, laterOrchestratedAs, orchestral suite]
-
A.
orchestratedFor
Indicates that one entity planned, coordinated, or arranged something specifically on behalf of or for the benefit of another entity.
-
B.
hasOrchestration
Indicates that one entity coordinates, manages, or sequences the actions or interactions of another entity or set of entities.
-
C.
hasOrchestrationBy
Indicates that something is organized, coordinated, or arranged by a specified agent or entity.
-
D.
usesOrchestration
Indicates that one entity employs orchestration mechanisms or tools to coordinate, manage, or automate the behavior and interactions of other entities or processes.
-
E.
laterPerformedBy
Indicates that an action or event is carried out by a particular agent at a later time than another referenced action or event.
- 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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fe5ec9028081909ae3d6fbe2f4cbbc |
completed | May 8, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69fe5e1d715881909fc516fafc707644 |
completed | May 8, 2026, 10:05 p.m. |
| PDg | Predicate description generation | batch_69fe5ec84910819094cb15269ace7c51 |
completed | May 8, 2026, 10:08 p.m. |
Created at: April 28, 2026, 1:26 p.m.