Triple
T26023436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Tsar’s Bride |
E647215
|
entity |
| Predicate | hasTenorRole |
P167279
|
FINISHED |
| Object | Lykov |
—
|
NE NERFINISHED |
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: Lykov | Statement: [The Tsar’s Bride, hasTenorRole, Lykov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTenorRole Context triple: [The Tsar’s Bride, hasTenorRole, Lykov]
-
A.
hasCapitalRole
Indicates that an entity holds an official role, function, or status specifically associated with a capital city.
-
B.
denotesTenure
Indicates that one entity holds or has held a position, role, or office at another entity for a specified period of time.
-
C.
hasSettlementRole
Indicates that an entity holds or is assigned a specific functional role or status within a settlement.
-
D.
hasGoverningRole
Indicates that one entity holds an official position of authority, control, or governance over another entity or domain.
-
E.
hasStructureRole
Indicates that an entity serves a specific functional or positional role within a larger structure or organizational arrangement.
- 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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f66a6468ec8190a43ed6cd8c797f42 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 22, 2026, 9:05 a.m.