Triple
T12704112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gilbert (lunar crater) |
E303534
|
entity |
| Predicate | hasRegolith |
P106435
|
FINISHED |
| Object | lunar 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: lunar regolith | Statement: [Gilbert (lunar crater), hasRegolith, lunar regolith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegolith Context triple: [Gilbert (lunar crater), hasRegolith, lunar regolith]
-
A.
hasRegolithDepth
Indicates the depth or thickness of a layer of regolith present on a surface or object.
-
B.
surfaceRegolithDepth_m
Indicates the measured thickness of the loose surface regolith layer at a location, expressed in meters.
-
C.
hasHeavilyCrateredSurface
Indicates that the subject’s surface is densely covered with impact craters, showing extensive cratering relative to typical surfaces.
-
D.
hasSatelliteCrater
Indicates that one crater is a secondary or subsidiary crater associated with, and typically located near, another primary crater.
-
E.
surfaceGeologyKnown
Indicates that the composition or characteristics of an entity’s surface geology have been determined or are known.
- 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_69d7bdef90d48190b46b88270e780946 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d962a32c6481908ddaddae4ea267bf |
completed | April 10, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69d960be63f081908a5ef5ef17a311bf |
completed | April 10, 2026, 8:42 p.m. |
| PDg | Predicate description generation | batch_69d96297b81c819081ad1432dc5f15f4 |
completed | April 10, 2026, 8:50 p.m. |
Created at: April 9, 2026, 5:23 p.m.