Triple
T19299433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lunae Planum |
E482653
|
entity |
| Predicate | surfaceMorphology |
P47694
|
FINISHED |
| Object | low-relief plain |
—
|
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-relief plain | Statement: [Lunae Planum, surfaceMorphology, low-relief plain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfaceMorphology Context triple: [Lunae Planum, surfaceMorphology, low-relief plain]
-
A.
surfaceEvolution
Indicates how a surface changes or transforms over time due to physical, chemical, or environmental processes.
-
B.
surfaceFeatureOf
chosen
Indicates that one entity is a surface-level characteristic, pattern, or feature belonging to or present on another entity.
-
C.
surfaceExpressionOf
Indicates that one entity is a specific surface-level manifestation or observable form of another underlying entity or concept.
-
D.
surfaceQuality
Indicates the condition or characteristics of an entity’s outer surface, such as its smoothness, roughness, or finish.
-
E.
surfaceFormedBy
Indicates that a surface is created, shaped, or defined as a result of a particular process, interaction, or set of contributing factors.
- 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_69d8e8d04d5c8190baa816986f2b1d1e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc8852208190ba0337a9623d9bdf |
completed | April 20, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:31 p.m.