Triple
T29140592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | In Loving Memory |
E738617
|
entity |
| Predicate | hasStrongWilledProtagonist |
P21469
|
FINISHED |
| Object | Ivy Unsworth |
—
|
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: Ivy Unsworth | Statement: [In Loving Memory, hasStrongWilledProtagonist, Ivy Unsworth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStrongWilledProtagonist Context triple: [In Loving Memory, hasStrongWilledProtagonist, Ivy Unsworth]
-
A.
protagonistMust
Indicates that a particular entity is required to serve as the main character or central focus within a narrative or scenario.
-
B.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
C.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
-
D.
protagonistCharacteristic
chosen
Indicates that a characteristic, trait, or defining quality is attributed to the protagonist in a narrative or scenario.
-
E.
hasHumanProtagonists
Indicates that the primary characters driving the narrative are human beings rather than non-human entities.
- 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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: April 28, 2026, 11:36 a.m.