Triple
T25641923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Launch Site One |
E642858
|
entity |
| Predicate | landingProfile |
P158952
|
FINISHED |
| Object | vertical landing of booster |
—
|
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: vertical landing of booster | Statement: [Launch Site One, landingProfile, vertical landing of booster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landingProfile Context triple: [Launch Site One, landingProfile, vertical landing of booster]
-
A.
landingPilot
Indicates that an entity is acting as the pilot responsible for landing an aircraft or spacecraft.
-
B.
landing
Indicates the action or event of an entity coming down from the air or a higher position to make controlled contact with a surface.
-
C.
profile
Indicates that one entity creates, presents, or analyzes a detailed description or representation of another entity’s characteristics or behavior.
-
D.
visitorProfile
Indicates a relationship where a profile encapsulates information or attributes associated with a particular visitor.
-
E.
profileElement
Indicates that something is a component or attribute within a larger profile structure.
- F. None of above. chosen
Provenance (4 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5faa11fa88190a7bb53c814995268 |
completed | May 2, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 21, 2026, 5:44 p.m.