Triple
T23479905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piedmont, New Mexico |
E570374
|
entity |
| Predicate | transportEventInStory |
P32261
|
FINISHED |
| Object | recovery of crashed satellite |
—
|
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: recovery of crashed satellite | Statement: [Piedmont, New Mexico, transportEventInStory, recovery of crashed satellite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportEventInStory Context triple: [Piedmont, New Mexico, transportEventInStory, recovery of crashed satellite]
-
A.
transportActivity
Indicates an activity in which something or someone is moved or carried from one place to another.
-
B.
hasTransportationEvent
chosen
Indicates that an entity is involved in or associated with a specific transportation-related occurrence, such as a trip, transfer, or movement event.
-
C.
travelsInVehicle
Indicates that an entity is moving from one place to another while being transported inside or on a vehicle.
-
D.
transportFrom
Indicates that something or someone is moved or carried away starting from a specified origin location.
-
E.
withinTravelTo
Indicates that one location is close enough to another that traveling between them is feasible or practical within a specified limit (such as time or distance).
- 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_69e245af8a88819084f2704f6d265a92 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a74f48d8819080e875aaea8b46b3 |
completed | April 29, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:02 p.m.