Triple
T32160494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lena Mainz |
E821408
|
entity |
| Predicate | isFocalCharacterIn |
P77485
|
FINISHED |
| Object | Three Lives |
—
|
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: Three Lives | Statement: [Lena Mainz, isFocalCharacterIn, Three Lives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFocalCharacterIn Context triple: [Lena Mainz, isFocalCharacterIn, Three Lives]
-
A.
isPivotalForCharacter
Indicates that something plays a crucial, defining role in shaping a character’s development, decisions, or narrative arc.
-
B.
characterInFocus
chosen
Indicates that a particular character is the primary subject or focal point within a given context, scene, or narrative segment.
-
C.
isFictionalCharacter
Indicates that the subject is a character that exists only in fiction rather than in real life.
-
D.
isCharacterInSetting
Indicates that a particular character appears or exists within a specified setting or environment.
-
E.
hasHumanCharacterRole
Indicates that an entity is assigned a role or function specifically associated with a human character within a context such as a story, performance, or representation.
- 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_69f34905e098819082191a6922a6d607 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6ba1a2d4c8190aa73a7b9b37c7c0d |
completed | May 3, 2026, 2:59 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:32 a.m.