Triple
T28842871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cannons |
E728368
|
entity |
| Predicate | employmentPeriodOfGeorgeFridericHandel |
P174381
|
FINISHED |
| Object | 1717–1719 |
—
|
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: 1717–1719 | Statement: [Cannons, employmentPeriodOfGeorgeFridericHandel, 1717–1719]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employmentPeriodOfGeorgeFridericHandel Context triple: [Cannons, employmentPeriodOfGeorgeFridericHandel, 1717–1719]
-
A.
BachWorkedHerePeriod
Indicates that Johann Sebastian Bach worked at this place during the specified time period.
-
B.
periodOfComposer
Indicates the historical or stylistic period during which a composer was active or to which their work is primarily associated.
-
C.
HandelComposedHere
Indicates that the composer George Frideric Handel created or composed a work at the specified location.
-
D.
employedAsKapellmeister
Indicates that one entity is employed in the role or position of Kapellmeister (music director/chapel master) for another entity.
-
E.
timePeriodOfCompositionOfOpera
Indicates the time span during which an opera was composed.
- 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_69f0319e8e7c8190b37288c8845b9dbc |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6c20f209081909fb9ac8f95069f04 |
completed | May 3, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c125695c81909704c67bef4ce5b2 |
completed | May 3, 2026, 3:29 a.m. |
Created at: April 28, 2026, 6:41 a.m.