Triple
T20330331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stickney crater |
E492458
|
entity |
| Predicate | regolithPresence |
P106435
|
FINISHED |
| Object | loose dusty material on floor |
—
|
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: loose dusty material on floor | Statement: [Stickney crater, regolithPresence, loose dusty material on floor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regolithPresence Context triple: [Stickney crater, regolithPresence, loose dusty material on floor]
-
A.
hasRegolith
chosen
Indicates that one entity possesses, contains, or is covered by regolith (a layer of loose, unconsolidated surface material).
-
B.
hasRegolithBehavior
Indicates that an entity exhibits or is associated with a specific type of behavior related to regolith (loose surface material such as soil, dust, or broken rock).
-
C.
hasRegolithDepth
Indicates the depth or thickness of a layer of regolith present on a surface or object.
-
D.
surfaceRegolithDepth_m
Indicates the measured thickness of the loose surface regolith layer at a location, expressed in meters.
-
E.
surfaceGeologyKnown
Indicates that the composition or characteristics of an entity’s surface geology have been determined or are known.
- 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_69e0b4a1a09881908d97270d6971a25a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e677e6f5d08190bedf376bbb999ebc |
completed | April 20, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:22 a.m.