Triple
T38092199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USOS |
E951143
|
entity |
| Predicate | supportsVisitingVehicle |
P172985
|
FINISHED |
| Object | Space Shuttle (retired) |
E208923
|
NE 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: Space Shuttle (retired) | Statement: [USOS, supportsVisitingVehicle, Space Shuttle (retired)]
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 (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_69f76f04960c8190a83f14ae4c67f5bc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4193b3907881908ff7ba8e3596aff4 |
completed | June 28, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.