Triple
T38092199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USOS |
E951143
|
entity |
| Predicate | supportsVisitingVehicle |
—
|
GENERATED |
| Object | Space Shuttle (retired) |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsVisitingVehicle Context triple: [USOS, supportsVisitingVehicle, Space Shuttle (retired)]
-
A.
visitingVehicle
chosen
Indicates a relationship where a vehicle temporarily arrives at or is present at a location that is not its usual or home base.
-
B.
allowsVehicles
Indicates that one entity permits vehicles to enter, use, or be present within another entity’s area or domain.
-
C.
supportsVehicle
Indicates that one entity provides the necessary strength, stability, or structure to bear the weight of a vehicle.
-
D.
hasVehicleAccess
Indicates that an entity is permitted to use or enter a particular vehicle.
-
E.
hasPrimaryVehicularAccessTo
Indicates that one location or entity serves as the main route or means by which vehicles can reach or enter another location or entity.
- F. None of above.
Provenance (1 batch)
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_69f76f04960c8190a83f14ae4c67f5bc |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.