Triple
T26643107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ares I |
E668830
|
entity |
| Predicate | crewCapacityPlanned |
P8587
|
FINISHED |
| Object | up to 6 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 6 astronauts | Statement: [Ares I, crewCapacityPlanned, up to 6 astronauts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewCapacityPlanned Context triple: [Ares I, crewCapacityPlanned, up to 6 astronauts]
-
A.
hasCrewCapacity
chosen
Indicates that an entity is capable of accommodating a specified number of crew members.
-
B.
aircraftCapacity
Indicates the maximum number of passengers or amount of load that an aircraft is designed or allowed to carry.
-
C.
designedCargoCapacity
Indicates the maximum amount of cargo an object (such as a vehicle or container) was originally engineered or specified to carry.
-
D.
crewAndPassengersCount
Indicates the total number of people on a vehicle or vessel, combining both crew members and passengers.
-
E.
launcherCapacity
Indicates the maximum number or size of items that a launcher is designed to hold or deploy.
- 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_69ee9d00eb5481908d6c6d0ada2f0c9a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f61633a2c481909c7c5992aaad6e5c |
completed | May 2, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 2:30 a.m.