Triple
T33383109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burning Secret |
E854835
|
entity |
| Predicate | motherCharacterRole |
P102151
|
FINISHED |
| Object | object of the baron's seduction |
—
|
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: object of the baron's seduction | Statement: [Burning Secret, motherCharacterRole, object of the baron's seduction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: motherCharacterRole Context triple: [Burning Secret, motherCharacterRole, object of the baron's seduction]
-
A.
motherCharacterName
Indicates that one character is the mother of another character, specifying a maternal parent-child relationship between them.
-
B.
motherCharacterBasedOn
Indicates that one mother character is created or written based on another specific character.
-
C.
playedMotherOfCharacter
Indicates that one person portrayed the mother of a specific character in a performance or production.
-
D.
motherRole
chosen
Indicates that one entity holds the role or function of a mother in relation to another entity.
-
E.
motherPortrayedBy
Indicates that a person’s mother is depicted or played by a particular actor or performer.
- 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_69f3496d54048190a1cb91fdd7caa6ea |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:35 a.m.