Triple
T19704688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ya imeni yeyo ne znayu |
E473181
|
entity |
| Predicate | operaNumberType |
P137013
|
FINISHED |
| Object | aria |
—
|
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: aria | Statement: [Ya imeni yeyo ne znayu, operaNumberType, aria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operaNumberType Context triple: [Ya imeni yeyo ne znayu, operaNumberType, aria]
-
A.
operaNumberInComposerOutput
Indicates the ordinal position or catalog number assigned to an opera within the complete body of works by a specific composer.
-
B.
estimatedNumberOfOperas
Indicates the approximate count of operas associated with an entity, rather than an exact, verified number.
-
C.
operaAct
Indicates that an entity performs in or takes part in an act (segment) of an opera performance.
-
D.
hasOpusNumber
Indicates that a musical work is associated with a specific opus number assigned to it, typically denoting its place in a composer’s catalog.
-
E.
operaNumberInMozartsOutput
Indicates the ordinal position or catalog number assigned to an opera within the complete body of Mozart’s operatic works.
- F. None of above. chosen
Provenance (4 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e642b998608190a82f23bbf77f7bd2 |
completed | April 20, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69e530438c60819082364c7be3eef6f0 |
completed | April 19, 2026, 7:42 p.m. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:46 p.m.