Triple
T24818500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyperion |
E620989
|
entity |
| Predicate | surfaceRegolith |
P106435
|
FINISHED |
| Object | very low-density, fluffy regolith |
—
|
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: very low-density, fluffy regolith | Statement: [Hyperion, surfaceRegolith, very low-density, fluffy regolith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfaceRegolith Context triple: [Hyperion, surfaceRegolith, very low-density, fluffy regolith]
-
A.
surfaceRegolithDepth_m
Indicates the measured thickness of the loose surface regolith layer at a location, expressed in meters.
-
B.
hasRegolith
chosen
Indicates that one entity possesses, contains, or is covered by regolith (a layer of loose, unconsolidated surface material).
-
C.
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).
-
D.
hasRegolithDepth
Indicates the depth or thickness of a layer of regolith present on a surface or object.
-
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_69e2fabfd4648190bd0e5c7f4dbb6cab |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:04 a.m.