Triple
T21105025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Loss of Roses |
E520015
|
entity |
| Predicate | hasCharacterDynamic |
P102538
|
FINISHED |
| Object | intergenerational conflict |
—
|
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: intergenerational conflict | Statement: [A Loss of Roses, hasCharacterDynamic, intergenerational conflict]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCharacterDynamic Context triple: [A Loss of Roses, hasCharacterDynamic, intergenerational conflict]
-
A.
dynamicCharacter
chosen
Indicates that a character undergoes significant internal change or development over the course of a narrative.
-
B.
hasCharacters
Indicates that an entity (such as a work or story) includes or features certain characters as part of its content.
-
C.
hasHumanCharacters
Indicates that the subject includes or features characters that are human beings.
-
D.
hasDroidCharacter
Indicates that an entity features or includes a character that is a droid.
-
E.
hasCharacterControl
Indicates that one entity has the ability or authority to direct, manipulate, or govern the behavior or state of another entity.
- 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_69e0b508d8dc81909be940dafe36c8f7 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e71b6150f08190a3738f1eda7fa834 |
completed | April 21, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69e5dbff56848190a03b350a9305c612 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:53 p.m.