Triple
T1922391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agon |
E40151
|
entity |
| Predicate | periodInComposerCareer |
P30618
|
FINISHED |
| Object | late Stravinsky period |
—
|
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: late Stravinsky period | Statement: [Agon, periodInComposerCareer, late Stravinsky period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodInComposerCareer Context triple: [Agon, periodInComposerCareer, late Stravinsky period]
-
A.
timeInArtistCareer
chosen
Indicates the point or period within an artist’s professional career at which a given event, work, or activity occurs.
-
B.
notableWorkPeriod
Indicates the time span during which an entity produced or was associated with its most significant or well-known works.
-
C.
activeYearsInCareer
Indicates the span of time during which an entity was actively engaged in a particular career or professional field.
-
D.
chronologyWithinArtistOeuvre
Indicates the temporal ordering of works within a single artist’s body of work, specifying how one piece relates in time to others by the same artist.
-
E.
activeYearsInFilm
Indicates the span of years during which an entity was actively involved in film-related work or roles.
- 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_69a8864298748190a2f2fd34f7ef8d77 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb233011881908736523d36f01b0c |
completed | March 7, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69abafed2ab481908920334e77b1021b |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.