Triple
T31793312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expedition 20 |
E811525
|
entity |
| Predicate | visitingVehicle |
P172985
|
FINISHED |
| Object | Space Shuttle Endeavour STS-127 |
—
|
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: Space Shuttle Endeavour STS-127 | Statement: [Expedition 20, visitingVehicle, Space Shuttle Endeavour STS-127]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitingVehicle Context triple: [Expedition 20, visitingVehicle, Space Shuttle Endeavour STS-127]
-
A.
hostVehicle
Indicates that one entity serves as the primary or reference vehicle in relation to another entity or context.
-
B.
intendedVehicle
Indicates that one entity is the vehicle that another entity plans or is meant to use.
-
C.
parentVehicle
Indicates that one vehicle serves as the primary or containing vehicle from which another vehicle is derived, owned, or hierarchically related.
-
D.
vehicleFor
Indicates that one entity serves as the means of transportation or conveyance for another entity.
-
E.
mainVehicle
Indicates that one vehicle is the primary or most important vehicle associated with a given entity or context.
- F. None of above. chosen
Provenance (4 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_69f348e60748819082dcaa7792659803 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b2d9aad88190a445f8f591cb19fc |
completed | May 3, 2026, 2:28 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b21da77081908c5c015c4606d344 |
completed | May 3, 2026, 2:25 a.m. |
Created at: April 30, 2026, 11:39 p.m.