Triple
T28842869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cannons |
E728368
|
entity |
| Predicate | hasResidentComposer |
P40861
|
FINISHED |
| Object | George Frideric Handel |
—
|
NE NERFINISHED |
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: George Frideric Handel | Statement: [Cannons, hasResidentComposer, George Frideric Handel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResidentComposer Context triple: [Cannons, hasResidentComposer, George Frideric Handel]
-
A.
hasComposerInResidence
chosen
Indicates that an organization or institution has officially appointed a specific composer to serve in a resident or ongoing compositional role.
-
B.
hasComposerResidence
Indicates that a composer has a particular place as their residence or primary dwelling.
-
C.
hasMusicalComposer
Indicates that one entity serves as the musical composer responsible for creating the music associated with another entity.
-
D.
hasBandMemberAsComposer
Indicates that a band has one of its own members serving as the composer of a musical work.
-
E.
hasMainComposerRole
Indicates that an entity holds the primary or leading composer role for a given work or production.
- 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_69f0319e8e7c8190b37288c8845b9dbc |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69ff80d9a1d88190a95b1488acd6e2e5 |
completed | May 9, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69ff802ae2dc819093a3cda42b63dcbd |
completed | May 9, 2026, 6:42 p.m. |
Created at: April 28, 2026, 6:41 a.m.