Triple
T18773761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enterprise Rupes |
E459080
|
entity |
| Predicate | RupesMeans |
P99754
|
FINISHED |
| Object | cliffs |
—
|
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: cliffs | Statement: [Enterprise Rupes, RupesMeans, cliffs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RupesMeans Context triple: [Enterprise Rupes, RupesMeans, cliffs]
-
A.
RheasilviaCentralPeakHeight
Indicates the measured vertical extent of the central peak within the Rheasilvia impact basin.
-
B.
equatorialRidgeHeight_km
Indicates the height, in kilometers, of a ridge or elevated feature located along or near the equator of an object.
-
C.
isCentralPeakOf
Indicates that one entity is the main, elevated peak located near the center of another, typically larger, geological or impact structure.
-
D.
equatorialRidgeLength_km
Indicates the length, measured in kilometers, of an object's ridge or ridge system located along or near its equator.
-
E.
hasAstronomicalFeature
chosen
Indicates that an entity possesses, contains, or is characterized by a specific astronomical feature (such as a star, planet, crater, or other celestial structure).
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e593378a4081909cc1b0856fce7d7d |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d1126e4819099607837ed5aadca |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.