Triple
T26275356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charley Pearl |
E660551
|
entity |
| Predicate | lifeStatusChange |
P160554
|
FINISHED |
| Object | life upended by romance |
—
|
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: life upended by romance | Statement: [Charley Pearl, lifeStatusChange, life upended by romance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifeStatusChange Context triple: [Charley Pearl, lifeStatusChange, life upended by romance]
-
A.
lifeStatus
Indicates the current state of an entity’s existence, such as whether it is alive, dead, or in another defined life condition.
-
B.
lifeStatusAtStart
Indicates the life status or condition of an entity at the beginning of a specified event or time period.
-
C.
marriageStatusChange
Indicates a change in an entity’s marital status from one state to another at a particular point in time.
-
D.
laterLifeEvent
Indicates that one event, condition, or action occurs during a later stage in an entity’s life relative to earlier life phases.
-
E.
legalStatusChangedIn
Indicates that an entity’s legal status was altered or reclassified within a specified jurisdiction, context, or time frame.
- F. None of above. chosen
Provenance (4 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_69ee812960d081909cff6085cc9fa3a6 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60e33c5748190abaa09d9b0c4c00a |
completed | May 2, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f6037bf7a081908862a8359be80cf8 |
completed | May 2, 2026, 2 p.m. |
Created at: April 26, 2026, 9:55 p.m.