Triple
T32366797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amundsen crater |
E827015
|
entity |
| Predicate | hasIlluminationProperty |
P173979
|
FINISHED |
| Object | contains permanently shadowed regions |
—
|
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: contains permanently shadowed regions | Statement: [Amundsen crater, hasIlluminationProperty, contains permanently shadowed regions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIlluminationProperty Context triple: [Amundsen crater, hasIlluminationProperty, contains permanently shadowed regions]
-
A.
isIlluminated
Indicates that one entity provides light to another entity, making it lit or visible.
-
B.
luminescenceCapability
Indicates the ability of an entity to emit light through luminescence.
-
C.
isIlluminatedBy
Indicates that one entity receives light from, or is lit up by, another entity.
-
D.
hasLumen
Indicates that one entity possesses or is characterized by a specific luminous intensity or light output measured in lumens.
-
E.
hasLightingEffect
Indicates that one entity applies, produces, or is associated with a particular lighting effect on another entity or environment.
- 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_69f349166d548190887b412fe908e2f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6be9e9e1881909c41e3189585cfd0 |
completed | May 3, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bb344bb48190a8089f29c0063ded |
completed | May 3, 2026, 3:04 a.m. |
Created at: May 1, 2026, 12:50 a.m.