Triple
T27845602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth Departure Stage |
E703811
|
entity |
| Predicate | designedForCrewedMissions |
P112535
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Earth Departure Stage, designedForCrewedMissions, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForCrewedMissions Context triple: [Earth Departure Stage, designedForCrewedMissions, true]
-
A.
launchesCrewedMissions
Indicates that an entity initiates and sends human-crewed space missions into space or to specific destinations.
-
B.
usedForHumanSpaceflight
chosen
Indicates that something is employed or designed to support, enable, or conduct space missions involving human astronauts.
-
C.
crewed
Indicates that an entity is operated, staffed, or manned by one or more people who serve as its crew.
-
D.
designedCrewVehicle
Indicates that an agent or entity is responsible for designing a vehicle intended to carry a crew.
-
E.
designedCrew
Indicates that one entity is responsible for planning, organizing, or creating the crew associated with another entity.
- 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_69ef840d9e3c819093615ebff4ec22be |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: April 27, 2026, 6:06 p.m.