Triple
T27996370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Starship SN8 |
E707023
|
entity |
| Predicate | vehicleStage |
P9657
|
FINISHED |
| Object | Starship upper stage |
—
|
NE NERFINISHED |
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: Starship upper stage | Statement: [Starship SN8, vehicleStage, Starship upper stage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vehicleStage Context triple: [Starship SN8, vehicleStage, Starship upper stage]
-
A.
stageOf
chosen
Indicates that one entity represents a particular phase, step, or developmental period within the progression or lifecycle of another entity.
-
B.
vehicleBase
Indicates that one entity serves as the foundational or underlying base for a vehicle-related entity or system.
-
C.
controlVehicle
Indicates having the authority or ability to direct, operate, or manage the movement and functioning of a vehicle.
-
D.
vehicleStandard
Indicates that something complies with, or is defined according to, a specified vehicle-related standard or regulatory specification.
-
E.
hostVehicle
Indicates that one entity serves as the primary or reference vehicle in relation to another entity or context.
- 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_69ef96b980d88190a753b2f9a978595a |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63fd79e4c8190af9263b679e5ff07 |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 7:53 p.m.