Triple
T18519305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iola Tornagi |
E452542
|
entity |
| Predicate | spouse’s notability |
P19181
|
FINISHED |
| Object | renowned Russian opera bass |
—
|
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: renowned Russian opera bass | Statement: [Iola Tornagi, spouse’s notability, renowned Russian opera bass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouse’s notability Context triple: [Iola Tornagi, spouse’s notability, renowned Russian opera bass]
-
A.
spouseNotableFor
chosen
Indicates that a person's spouse is recognized or distinguished for a particular achievement, role, or characteristic.
-
B.
spouseNotableAward
Indicates that a person’s spouse has received a notable award or honor.
-
C.
spouseNotableWorkField
Indicates that the notable work or professional field associated with a person’s spouse is being specified.
-
D.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
-
E.
spouseRecognition
Indicates that one entity formally acknowledges another entity as their spouse within a recognized relationship.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5338ce7e481908ee69ffe4f30d5a4 |
completed | April 19, 2026, 7:57 p.m. |
| PD | Predicate disambiguation | batch_69e469e0025c81908f16ed4f922674af |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:36 a.m.