Triple
T30310967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Recondita armonia |
E770921
|
entity |
| Predicate | singerCharacterProfession |
P169071
|
FINISHED |
| Object | painter |
—
|
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: painter | Statement: [Recondita armonia, singerCharacterProfession, painter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: singerCharacterProfession Context triple: [Recondita armonia, singerCharacterProfession, painter]
-
A.
singerInteractsWithCharacter
Indicates that a singer engages in some form of interaction or exchange with a character.
-
B.
singerForCharacter
Indicates that one entity serves as the singing voice or vocalist for a particular character.
-
C.
isSingerFrom
Indicates that a person is a singer who originates from or is associated with a particular place or region.
-
D.
singerVoiceActor
Indicates that the subject is both a singer and a voice actor for the object, or performs voice-acting roles in addition to singing in relation to the object.
-
E.
performerCharacterName
Indicates that a performer is associated with or portrays a specific character name in a performance or work.
- 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6816c17e08190b543186d578dca88 |
completed | May 2, 2026, 10:57 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676c35f3481909b9ba18a5662d6ce |
completed | May 2, 2026, 10:12 p.m. |
Created at: April 29, 2026, 7:50 p.m.