Triple
T26498342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sean Jones |
E669345
|
entity |
| Predicate | departureLocationInPlot |
P46825
|
FINISHED |
| Object | Hawaii |
—
|
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: Hawaii | Statement: [Sean Jones, departureLocationInPlot, Hawaii]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: departureLocationInPlot Context triple: [Sean Jones, departureLocationInPlot, Hawaii]
-
A.
placeOfDeparture
Indicates the location from which an entity, such as a person or vehicle, begins its journey or movement.
-
B.
departsFrom
chosen
Indicates that an entity (such as a vehicle, person, or process) begins its movement, journey, or operation starting from a specified location or point of origin.
-
C.
departurePointInCityCentre
Indicates that the departure point of an entity (such as a trip, route, or service) is located within the central area of a city.
-
D.
landingPlace
Indicates the location or surface where something or someone comes down to rest after moving through the air or space.
-
E.
departureStory
Indicates a narrative or account describing how, why, and under what circumstances an entity left or departed from a place, role, or situation.
- 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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61a17a7788190946f7e32d63cd43f |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
Created at: April 27, 2026, 1:10 a.m.