Triple
T36626462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SLF Runway 15 |
E904180
|
entity |
| Predicate | notableLandingType |
P16151
|
FINISHED |
| Object | orbiter landing |
—
|
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: orbiter landing | Statement: [SLF Runway 15, notableLandingType, orbiter landing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLandingType Context triple: [SLF Runway 15, notableLandingType, orbiter landing]
-
A.
landingMethod
Indicates the manner or technique by which something or someone arrives and comes to rest at a destination, typically from the air or space.
-
B.
hasLandingCharacteristics
Indicates that an entity possesses specific attributes or features related to how it lands or is capable of landing.
-
C.
typeOfLanding
chosen
Indicates the specific kind or category of landing that occurs in a given event or situation.
-
D.
landingMass
Indicates the mass of an object or vehicle at the moment it lands.
-
E.
landedNear
Indicates that one entity has come to rest on a surface or location in close proximity to another specified entity or reference point.
- 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.