Triple
T30716647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ann Hasseltine Judson |
E782039
|
entity |
| Predicate | departureLocationForMission |
P1521
|
FINISHED |
| Object | Salem, Massachusetts |
—
|
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: Salem, Massachusetts | Statement: [Ann Hasseltine Judson, departureLocationForMission, Salem, Massachusetts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: departureLocationForMission Context triple: [Ann Hasseltine Judson, departureLocationForMission, Salem, Massachusetts]
-
A.
placeOfDeparture
chosen
Indicates the location from which an entity, such as a person or vehicle, begins its journey or movement.
-
B.
departsFrom
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.
placeOfMission
Indicates the location where a mission, assignment, or task is carried out or based.
-
D.
landingPlace
Indicates the location or surface where something or someone comes down to rest after moving through the air or space.
-
E.
destinationAirportLocation
Indicates the geographic location associated with the airport that serves as the destination in a trip or flight.
- 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_69f224acd24481908ed5f96f0d69b5dd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:35 p.m.