Triple
T21031432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reinhold (lunar crater) |
E518071
|
entity |
| Predicate | hasErosionState |
P139016
|
FINISHED |
| Object | relatively well preserved |
—
|
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: relatively well preserved | Statement: [Reinhold (lunar crater), hasErosionState, relatively well preserved]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasErosionState Context triple: [Reinhold (lunar crater), hasErosionState, relatively well preserved]
-
A.
hasErosionalState
chosen
Indicates the current degree or condition of erosion affecting an entity’s surface or structure.
-
B.
hasErosionFeature
Indicates that one entity exhibits or contains a specific erosion-related feature or form resulting from erosional processes.
-
C.
hasErosionEffect
Indicates that one entity causes or exhibits an erosive impact or degradation effect on another entity or surface.
-
D.
erosionRate
Indicates the rate at which material is worn away or removed from a surface over time due to erosive processes.
-
E.
erosionResistance
Indicates how strongly one entity can withstand or prevent being worn away, degraded, or removed by erosive forces caused by another entity or the environment.
- 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_69e0b503275c8190afd9a163f997c709 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc82b5348190b449d59e6cada9de |
completed | April 21, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf6728881908a2a43a5c8804a2a |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:55 p.m.