Triple
T8469134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genoveva, Op. 81 |
E200236
|
entity |
| Predicate | composerLifespan |
P27074
|
FINISHED |
| Object | 1810–1856 |
—
|
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: 1810–1856 | Statement: [Genoveva, Op. 81, composerLifespan, 1810–1856]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: composerLifespan Context triple: [Genoveva, Op. 81, composerLifespan, 1810–1856]
-
A.
composer
Indicates that one entity is the creator or writer of a musical work associated with another entity.
-
B.
lifecycleFeature
Indicates that one entity is a feature, phase, or characteristic associated with a particular stage in the lifecycle of another entity.
-
C.
designLifetime
Indicates the intended duration or operational period for which something is designed to function as specified.
-
D.
lifecycleType
Indicates the specific stage or pattern within an entity’s overall lifecycle that characterizes how it begins, evolves, and ends.
-
E.
creatorLifespan
chosen
Indicates the time period between the birth and death of the creator associated with an entity.
- 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4d5dd088190a79050417f527f14 |
completed | March 31, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69cbd10072cc819084be1ed9ac7ebe9d |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:11 p.m.