Triple
T19012772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gremin |
E465268
|
entity |
| Predicate | ariaTitle |
P134118
|
FINISHED |
| Object | Lyubvi vse vozrasty pokorny (All ages are submissive to love) |
—
|
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: Lyubvi vse vozrasty pokorny (All ages are submissive to love) | Statement: [Gremin, ariaTitle, Lyubvi vse vozrasty pokorny (All ages are submissive to love)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ariaTitle Context triple: [Gremin, ariaTitle, Lyubvi vse vozrasty pokorny (All ages are submissive to love)]
-
A.
altLabel
Indicates an alternative name, label, or synonym used to refer to the same entity as the primary label.
-
B.
associatedTitle
Indicates that one entity has a title, designation, or formal label that is linked or relevant to another entity.
-
C.
title
Indicates that one entity serves as the formal name or designation of another entity.
-
D.
eraTitleWith
Indicates a relationship where a specific era is associated with or designated by a particular title.
-
E.
usesTitle
Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
- 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_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. |
| PDg | Predicate description generation | batch_69e4ad8e075c8190ad561edc5e520057 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 12:02 p.m.