Triple
T30310979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Recondita armonia |
E770921
|
entity |
| Predicate | characterReflectsOn |
P195641
|
FINISHED |
| Object | Floria Tosca |
—
|
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: Floria Tosca | Statement: [Recondita armonia, characterReflectsOn, Floria Tosca]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterReflectsOn Context triple: [Recondita armonia, characterReflectsOn, Floria Tosca]
-
A.
dialoguesReflect
Indicates that the content or style of dialogues mirrors, represents, or reveals certain underlying ideas, themes, or characteristics.
-
B.
characterReveals
Indicates that one character discloses or makes known information, feelings, or intentions to another character.
-
C.
character1
Indicates that the subject is identified as the first or primary character in a narrative or context.
-
D.
characterMotivation
Indicates the underlying reasons, desires, or goals that drive a character’s actions and decisions within a narrative.
-
E.
characterInspiration
Indicates that one entity serves as the creative or conceptual inspiration for the development or portrayal of another character.
- 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_69fddd373cdc8190be1b12e70e4deb1f |
completed | May 8, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69fddc6915a88190ad41e379aa3ede13 |
completed | May 8, 2026, 12:51 p.m. |
| PDg | Predicate description generation | batch_69fddd364c1481908794c9d423bdc2d7 |
completed | May 8, 2026, 12:55 p.m. |
Created at: April 29, 2026, 7:50 p.m.