Triple
T38502980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brian Lackey |
E919889
|
entity |
| Predicate | travelsPurpose |
P102055
|
FINISHED |
| Object | to confront his past and find Neil McCormick |
—
|
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 confront his past and find Neil McCormick | Statement: [Brian Lackey, travelsPurpose, to confront his past and find Neil McCormick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelsPurpose Context triple: [Brian Lackey, travelsPurpose, to confront his past and find Neil McCormick]
-
A.
journeyPurpose
chosen
Indicates the reason or intended goal motivating an entity’s journey or trip.
-
B.
travelsFor
Indicates that one entity moves from place to place on behalf of, or for the benefit or purpose of, another entity or objective.
-
C.
typicalJourneyPurpose
Indicates the usual or most common reason or objective for which an entity undertakes a journey.
-
D.
sunJourneyPurpose
Indicates the purpose or intended goal behind a sun-related journey or movement.
-
E.
transportPurpose
Indicates that one entity is transported or moved specifically for the purpose, goal, or intended use denoted by 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_69f76e9ddd4481908f8c04439d848f9d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: May 3, 2026, 4:31 p.m.