Triple
T5458771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dream Chaser spaceplane |
E122543
|
entity |
| Predicate | crewCapacityPotential |
P8587
|
FINISHED |
| Object | up to 7 astronauts |
—
|
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: up to 7 astronauts | Statement: [Dream Chaser spaceplane, crewCapacityPotential, up to 7 astronauts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewCapacityPotential Context triple: [Dream Chaser spaceplane, crewCapacityPotential, up to 7 astronauts]
-
A.
hasCrewCapacity
chosen
Indicates that an entity is capable of accommodating a specified number of crew members.
-
B.
maximumPassengerCapacity
Indicates the greatest number of passengers that an entity is designed or allowed to carry at one time.
-
C.
designedCargoCapacity
Indicates the maximum amount of cargo an object (such as a vehicle or container) was originally engineered or specified to carry.
-
D.
aircraftCapacity
Indicates the maximum number of passengers or amount of load that an aircraft is designed or allowed to carry.
-
E.
cargoCapacityFeature
Indicates that an entity has a feature specifying how much cargo it can carry or accommodate.
- 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_69bd46424248819085282ddf50a565f3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd927c946c8190aef40679199fede3 |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a0d96c8190bd1299edbf764bbb |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:08 p.m.