Triple
T33856345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edith |
E867785
|
entity |
| Predicate | plansForLifeChange |
P66258
|
FINISHED |
| Object | to start a new life with Phil |
—
|
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: to start a new life with Phil | Statement: [Edith, plansForLifeChange, to start a new life with Phil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plansForLifeChange Context triple: [Edith, plansForLifeChange, to start a new life with Phil]
-
A.
planEffectiveFor
Indicates that a particular plan is suitable or successful in achieving desired outcomes for a given entity, context, or objective.
-
B.
inspiredActionPlan
Indicates that one entity’s example, ideas, or influence motivated another entity to create or adopt a specific course of action or plan.
-
C.
planning
chosen
Indicates that an entity is engaged in organizing or devising a future action, event, or course of behavior involving another entity or entities.
-
D.
planningChallenge
Indicates a situation where creating, organizing, or coordinating a plan is difficult or problematic for the involved entities.
-
E.
planningProcess
Indicates a relationship where an entity is engaged in or associated with the structured activity of defining goals, strategies, and steps to achieve a desired outcome.
- 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_69f349943ccc8190a3c41a3e0ae46cbf |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:47 a.m.