Triple
T33194491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kenneth S. Reightler Jr. |
E849714
|
entity |
| Predicate | operatorOnVehicle |
P144304
|
FINISHED |
| Object | Space Shuttle Discovery |
—
|
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 Discovery | Statement: [Kenneth S. Reightler Jr., operatorOnVehicle, Space Shuttle Discovery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorOnVehicle Context triple: [Kenneth S. Reightler Jr., operatorOnVehicle, Space Shuttle Discovery]
-
A.
controlVehicle
chosen
Indicates having the authority or ability to direct, operate, or manage the movement and functioning of a vehicle.
-
B.
vehicleInteraction
Indicates an interaction or relationship occurring between two or more vehicles, such as influencing each other’s movement, position, or behavior.
-
C.
vehicleFunction
Indicates the functional role or primary purpose that a vehicle is designed or used to perform.
-
D.
commandedVehicle
Indicates that one entity had authoritative control over or issued orders to another entity that is a vehicle.
-
E.
mountVehicle
Indicates initiating the action of getting onto or into a vehicle in order to use or ride it.
- 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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0062e6bd788190a7b4f3e5befb5cbb |
completed | May 10, 2026, 10:50 a.m. |
| PD | Predicate disambiguation | batch_6a0061989d188190b4815b2de3e8676f |
completed | May 10, 2026, 10:44 a.m. |
Created at: May 1, 2026, 1:29 a.m.