Triple
T29325505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ballet for Martha |
E743630
|
entity |
| Predicate | laterTitled |
P125915
|
FINISHED |
| Object | Appalachian Spring |
E202830
|
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: Appalachian Spring | Statement: [Ballet for Martha, laterTitled, Appalachian Spring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterTitled Context triple: [Ballet for Martha, laterTitled, Appalachian Spring]
-
A.
laterTitleHolder
Indicates that one entity is a subsequent holder of a particular title or position previously held by another entity.
-
B.
hasLaterTitle
Indicates that one title occurs chronologically after another title in a sequence or timeline.
-
C.
laterTitleUsage
Indicates that a title is used or applied to an entity at a later time or in a subsequent context relative to an earlier title usage.
-
D.
laterAdaptationName
chosen
Indicates that the object is the name of a later adaptation derived from or based on the subject.
-
E.
laterIn
Indicates that one event, state, or time point occurs after another in temporal order.
- 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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fe5d58c3e48190910aa3c23485e2c4 |
completed | May 8, 2026, 10:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a25c0ea881c8190b36c502ba5bf5c7a |
completed | June 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fe5c92090c8190bcfa412c0a3619df |
completed | May 8, 2026, 9:58 p.m. |
Created at: April 28, 2026, 1:26 p.m.