Triple
T27343319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enterprise (OV-101) |
E684167
|
entity |
| Predicate | suborbitalFlights |
P52278
|
FINISHED |
| Object | 0 |
—
|
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: 0 | Statement: [Enterprise (OV-101), suborbitalFlights, 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suborbitalFlights Context triple: [Enterprise (OV-101), suborbitalFlights, 0]
-
A.
suborbitalRange
Indicates the maximum distance or extent that something can travel or operate along a suborbital trajectory.
-
B.
reachedSuborbitalAltitude
chosen
Indicates that an object or vehicle has ascended to an altitude high enough to be considered suborbital, without achieving full orbital velocity.
-
C.
firstSuborbitalFlightDate
Indicates the calendar date on which an entity’s first suborbital flight occurred.
-
D.
firstFullyCrewedSuborbitalFlightFrom
Indicates that an entity is the launch site or location from which another entity conducted its first fully crewed suborbital spaceflight.
-
E.
spaceflightType
Indicates the specific category or mode of spaceflight associated with an entity, such as orbital, suborbital, interplanetary, or other mission types.
- 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 11:44 a.m.