Triple
T32279999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shoemaker crater |
E824662
|
entity |
| Predicate | hasIlluminationSource |
P66297
|
FINISHED |
| Object | indirect scattered light only |
—
|
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: indirect scattered light only | Statement: [Shoemaker crater, hasIlluminationSource, indirect scattered light only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIlluminationSource Context triple: [Shoemaker crater, hasIlluminationSource, indirect scattered light only]
-
A.
isIlluminatedBy
Indicates that one entity receives light from, or is lit up by, another entity.
-
B.
isIlluminated
Indicates that one entity provides light to another entity, making it lit or visible.
-
C.
hasLighting
Indicates that one entity is equipped with, contains, or is characterized by a particular type or configuration of lighting.
-
D.
hasLanternLightSource
Indicates that an entity uses a lantern as its source of light.
-
E.
hasRelatedIlluminant
chosen
Indicates that one entity is associated with another entity that serves as a corresponding or contextually relevant illuminant (light source) for it.
- 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_69f3490f404081908450db66884f4334 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bcc7edfc81909d0008fa9364de54 |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:43 a.m.