Triple
T32592938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Straight Story |
E833118
|
entity |
| Predicate | hasJourneyGoal |
P102055
|
FINISHED |
| Object | reconcile with estranged brother |
—
|
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: reconcile with estranged brother | Statement: [The Straight Story, hasJourneyGoal, reconcile with estranged brother]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJourneyGoal Context triple: [The Straight Story, hasJourneyGoal, reconcile with estranged brother]
-
A.
hasPlanningGoal
Indicates that an entity is associated with, or directed toward achieving, a specific planning objective or target state.
-
B.
hasProgramGoal
Indicates that an entity (such as a program or initiative) is associated with a specific intended goal or objective it aims to achieve.
-
C.
hasPrimaryGoal
Indicates that an entity’s main or most important objective is the specified goal.
-
D.
journeyPurpose
chosen
Indicates the reason or intended goal motivating an entity’s journey or trip.
-
E.
requiresJourneyOf
Indicates that one entity can only be achieved, accessed, or completed by undertaking a journey or progression involving another entity.
- 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_69f34929ff648190aded9424aa7564ae |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:05 a.m.