Triple
T14778236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nadine Franklin |
E347318
|
entity |
| Predicate | significantLifeEvent |
P53982
|
FINISHED |
| Object | death of her father |
—
|
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: death of her father | Statement: [Nadine Franklin, significantLifeEvent, death of her father]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantLifeEvent Context triple: [Nadine Franklin, significantLifeEvent, death of her father]
-
A.
significantEvent
Indicates that an event involving the entities is of notable importance or impact within a given context.
-
B.
significantEventType
Indicates the specific category or kind of major or noteworthy event associated with an entity or situation.
-
C.
notableEventInLife
chosen
Indicates that a particular event holds significant importance or impact within an entity’s life or personal history.
-
D.
significantEventInvolves
Indicates that a significant event includes or engages a particular entity as a participant or key element.
-
E.
significantEventEnd
Indicates the point in time when a significant event or occurrence comes to a close or is considered finished.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec817c39081909b08a0ffdfce9936 |
completed | April 14, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69de8c02e5c08190943c27594026faf7 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.