Triple
T19012745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lensky – tenor |
E465267
|
entity |
| Predicate | standardCasting |
P11865
|
FINISHED |
| Object | sung by a classically trained operatic tenor |
—
|
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: sung by a classically trained operatic tenor | Statement: [Lensky – tenor, standardCasting, sung by a classically trained operatic tenor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardCasting Context triple: [Lensky – tenor, standardCasting, sung by a classically trained operatic tenor]
-
A.
typicalCasting
chosen
Indicates that one entity is the usual or standard casting choice for portraying another entity (such as a role, character, or type).
-
B.
standardType
Indicates that one entity is classified as the standard, canonical, or reference type for another entity or context.
-
C.
standardPar
Indicates that two entities are parallel and conform to a recognized or defined standard of parallelism.
-
D.
coreStandard
Indicates that something conforms to, is defined by, or is governed by a central or foundational standard or specification.
-
E.
standardCreated
Indicates that an entity is responsible for the creation or establishment of a particular standard.
- 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.