Triple
T18594632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bonnie Nolan |
E454460
|
entity |
| Predicate | majorLifeEvent |
P53982
|
FINISHED |
| Object | leaves her marriage |
—
|
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: leaves her marriage | Statement: [Bonnie Nolan, majorLifeEvent, leaves her marriage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorLifeEvent Context triple: [Bonnie Nolan, majorLifeEvent, leaves her marriage]
-
A.
laterLifeEvent
Indicates that one event, condition, or action occurs during a later stage in an entity’s life relative to earlier life phases.
-
B.
notableEventInLife
chosen
Indicates that a particular event holds significant importance or impact within an entity’s life or personal history.
-
C.
significantEvent
Indicates that an event involving the entities is of notable importance or impact within a given context.
-
D.
settingOfLifeEvents
Indicates the location or environment in which significant life events of an entity take place.
-
E.
significantEventType
Indicates the specific category or kind of major or noteworthy event associated with an entity or situation.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e545b8d76881909db1539c7150befb |
completed | April 19, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:44 a.m.