Triple
T26871898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jim Gallien |
E676632
|
entity |
| Predicate | droppedOffChristopherMcCandlessNear |
P161551
|
FINISHED |
| Object | Healy, Alaska |
—
|
NE NERFINISHED |
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: Healy, Alaska | Statement: [Jim Gallien, droppedOffChristopherMcCandlessNear, Healy, Alaska]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: droppedOffChristopherMcCandlessNear Context triple: [Jim Gallien, droppedOffChristopherMcCandlessNear, Healy, Alaska]
-
A.
droppedOffChristopherMcCandlessNear
chosen
Indicates that one entity transported Christopher McCandless and left him at or near a specified location.
-
B.
lostAt
Indicates that an entity ceased to be in possession of or unable to be found at a specific location or context.
-
C.
reachedFromTrailhead
Indicates that a location or point can be accessed by traveling from a designated trailhead.
-
D.
diedDuringExpeditionTo
Indicates that an entity died while participating in or as a consequence of a specific expedition to a particular place or destination.
-
E.
diedOnJourneyBetween
Indicates that an entity died while traveling between two specified locations or points in 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_69eee9bb44988190b6e11652d028bc59 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61fd623bc819091df736cf3419b99 |
completed | May 2, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 5:33 a.m.