Triple
T23016825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mare Crisium |
E573050
|
entity |
| Predicate | hasMeanElevation |
P28306
|
FINISHED |
| Object | lower than surrounding highlands |
—
|
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: lower than surrounding highlands | Statement: [Mare Crisium, hasMeanElevation, lower than surrounding highlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMeanElevation Context triple: [Mare Crisium, hasMeanElevation, lower than surrounding highlands]
-
A.
hasAverageElevation
chosen
Indicates that an entity is characterized by a specific mean height above a defined reference level, typically sea level.
-
B.
hasElevationFeature
Indicates that one entity possesses or is characterized by a particular elevation-related feature or attribute, such as height, altitude, or vertical relief.
-
C.
hasTypicalElevationRelativeTo
Indicates the usual height or altitude of one entity in comparison to a referenced baseline or other entity.
-
D.
hasTopElevation
Indicates that an entity has a specified maximum or highest elevation value.
-
E.
hasElevationRelativeToSeaLevel
Indicates the elevation or height of an entity measured relative to mean sea level.
- 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_69e245b764cc8190a51be76f1d9611e1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f183e59a1c8190b8048a399a4727cb |
completed | April 29, 2026, 4:07 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:52 p.m.