Triple
T8152641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gioachino Rossini |
E190366
|
entity |
| Predicate | yearsActiveAsComposer |
P30618
|
FINISHED |
| Object | c. 1808–1829 |
—
|
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: c. 1808–1829 | Statement: [Gioachino Rossini, yearsActiveAsComposer, c. 1808–1829]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearsActiveAsComposer Context triple: [Gioachino Rossini, yearsActiveAsComposer, c. 1808–1829]
-
A.
publishedComposer
Indicates that a composer has had their musical works formally published, typically by a recognized publisher or label.
-
B.
timeInArtistCareer
chosen
Indicates the point or period within an artist’s professional career at which a given event, work, or activity occurs.
-
C.
hasMusicalComposer
Indicates that one entity serves as the musical composer responsible for creating the music associated with another entity.
-
D.
hasWrittenSongsFor
Indicates that one entity has composed songs specifically intended to be performed, recorded, or used by another entity.
-
E.
hasComposerInResidence
Indicates that an organization or institution has officially appointed a specific composer to serve in a resident or ongoing compositional role.
- 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_69ca82be7ba8819087de0147e9292c83 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb44d4494c8190aad2ee302e90670f |
completed | March 31, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69cb36a0847c8190af9038aef78319b3 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:37 p.m.