Triple
T28717026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pathfinder lander |
E729986
|
entity |
| Predicate | usedLandingSystem |
P124735
|
FINISHED |
| Object | airbags |
—
|
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: airbags | Statement: [Pathfinder lander, usedLandingSystem, airbags]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedLandingSystem Context triple: [Pathfinder lander, usedLandingSystem, airbags]
-
A.
usesGroundSystem
Indicates that one entity operates, relies on, or interacts with a particular ground-based system to perform its functions or services.
-
B.
hasLandingSystem
chosen
Indicates that an entity is equipped with or utilizes a particular landing system for performing landings.
-
C.
hasRunwayUse
Indicates that a particular runway is authorized or designated for use by a specific aircraft, operation, or purpose.
-
D.
hasLandingFacilities
Indicates that a location or structure is equipped with facilities that allow aircraft or other vehicles to land there.
-
E.
hasLandingConditions
Indicates the specific conditions or requirements that must be met for a landing to occur or be permitted.
- 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 5:51 a.m.