Triple
T19012732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lensky – tenor |
E465267
|
entity |
| Predicate | commonRepertoireCategory |
P29075
|
FINISHED |
| Object | standard lyric tenor repertoire |
—
|
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: standard lyric tenor repertoire | Statement: [Lensky – tenor, commonRepertoireCategory, standard lyric tenor repertoire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonRepertoireCategory Context triple: [Lensky – tenor, commonRepertoireCategory, standard lyric tenor repertoire]
-
A.
centralRepertoireFor
Indicates that something serves as a primary or core collection of works, items, or elements for a particular entity or context.
-
B.
uniformCategory
Indicates that two or more entities share the same classification or type within a defined category system.
-
C.
statusWithinRepertoire
Indicates that a particular status or state is included as part of an entity’s defined repertoire of possible statuses.
-
D.
collectionRole
Indicates the specific function, responsibility, or position an entity holds within a collection or grouped set of items.
-
E.
canonicalCategory
chosen
Indicates that an entity is assigned to its primary or standard category within a classification system.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6a9bac8819093f9af57000667b0 |
completed | April 20, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69e4a2fd80c081908237317a3a883e1c |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.