Triple
T11509445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surveyor 1 |
E272869
|
entity |
| Predicate | landingVelocity |
P99864
|
FINISHED |
| Object | approximately 3 meters per second |
—
|
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: approximately 3 meters per second | Statement: [Surveyor 1, landingVelocity, approximately 3 meters per second]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landingVelocity Context triple: [Surveyor 1, landingVelocity, approximately 3 meters per second]
-
A.
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.
-
B.
landingGLoad
Indicates the g-force experienced by an aircraft or object at the moment of 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.
landingMass
Indicates the mass of an object or vehicle at the moment it lands.
-
E.
landingRequires
Indicates that performing a landing action is contingent upon satisfying a specified requirement or precondition.
- 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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d86db65eb081908613a1002c6a4fb4 |
completed | April 10, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69d80876e5f0819088cff2e72f773cf6 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d822ef46988190a1c360da4ee14fef |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 8, 2026, 9:36 p.m.