Triple
T4065989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DAN |
E86323
|
entity |
| Predicate | depthSensitivity |
P16570
|
FINISHED |
| Object | up to about 1 meter below Martian surface |
—
|
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: up to about 1 meter below Martian surface | Statement: [DAN, depthSensitivity, up to about 1 meter below Martian surface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depthSensitivity Context triple: [DAN, depthSensitivity, up to about 1 meter below Martian surface]
-
A.
depth
Indicates the vertical distance from a reference surface or top point down to a lower point or bottom within a medium or space.
-
B.
depthClass
Indicates the categorical classification of an entity based on its depth or depth-related range.
-
C.
depthMetresApprox
chosen
Indicates an approximate measurement of how deep something is in metres, rather than an exact value.
-
D.
sensorResolution
Indicates the level of detail or precision with which a sensor can measure or distinguish changes in the observed quantity or environment.
-
E.
sensitivityFeature
Indicates a relationship where one entity functions as a sensitivity-related characteristic, parameter, or attribute of another entity.
- 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_69aed93c69208190a4efac0efe3cd69b |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefbf58d9c8190936e453b0d397cb0 |
completed | March 9, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69aef9061d2481908307cafc9e9b32c0 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:38 p.m.