Triple
T33212333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elysium Planitia |
E850192
|
entity |
| Predicate | hasRelativeCraterDensity |
P59618
|
FINISHED |
| Object | low |
—
|
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: low | Statement: [Elysium Planitia, hasRelativeCraterDensity, low]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelativeCraterDensity Context triple: [Elysium Planitia, hasRelativeCraterDensity, low]
-
A.
hasCraterDensity
chosen
Indicates a relationship where an entity is characterized by a specific density or concentration of craters on its surface.
-
B.
craterDensity
Indicates the measured concentration of impact craters on a surface area, reflecting how densely craters are distributed.
-
C.
hasOverlappingCrater
Indicates that one crater partially or fully overlaps another crater in space, sharing a common area of their surfaces.
-
D.
hasSatelliteCrater
Indicates that one crater is a secondary or subsidiary crater associated with, and typically located near, another primary crater.
-
E.
hasHeavilyCrateredSurface
Indicates that the subject’s surface is densely covered with impact craters, showing extensive cratering relative to typical surfaces.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a035ead9ee0819099806d2670dc9c50 |
completed | May 12, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_6a035dc9210c8190a9044c6a53211520 |
completed | May 12, 2026, 5:05 p.m. |
Created at: May 1, 2026, 1:30 a.m.