Triple
T6079810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-58 |
E135492
|
entity |
| Predicate | landingMass |
P68528
|
FINISHED |
| Object | 93,000 kg |
—
|
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: 93,000 kg | Statement: [STS-58, landingMass, 93,000 kg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landingMass Context triple: [STS-58, landingMass, 93,000 kg]
-
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.
landingOperation
Indicates an operation in which an aircraft, spacecraft, or similar vehicle descends and makes contact with a surface to complete its landing.
-
C.
landingDistance
Indicates the required or actual distance needed for an aircraft or object to complete a landing from approach to full stop.
-
D.
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.
-
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. 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_69c0087ad31c8190ab936e0ff28614b6 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0577209b88190afe5b1365cf6436d |
completed | March 22, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69c049f21fe08190995df3c5c05fb8ea |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8d4a148190bd8f95caae978e1b |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:11 p.m.