Triple
T15622493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Addie Bundren |
E375591
|
entity |
| Predicate | causeOfJourney |
P102055
|
FINISHED |
| Object | desire to be buried in Jefferson, Mississippi |
—
|
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: desire to be buried in Jefferson, Mississippi | Statement: [Addie Bundren, causeOfJourney, desire to be buried in Jefferson, Mississippi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfJourney Context triple: [Addie Bundren, causeOfJourney, desire to be buried in Jefferson, Mississippi]
-
A.
journeyPurpose
chosen
Indicates the reason or intended goal motivating an entity’s journey or trip.
-
B.
causeOfChangeOfDestination
Indicates that one entity is the reason or trigger for another entity changing its intended destination.
-
C.
journeyFrom
Indicates that an entity undertakes or originates a journey starting from a specified location or source.
-
D.
sunJourneyPurpose
Indicates the purpose or intended goal behind a sun-related journey or movement.
-
E.
typicalJourneyPurpose
Indicates the usual or most common reason or objective for which an entity undertakes a journey.
- 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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e9a95f08190b0013ba1428849d3 |
completed | April 16, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69deda868d4481908f4bce1c64d2902a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:14 a.m.