Triple
T6042830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mare Tranquillitatis |
E134588
|
entity |
| Predicate | hasGravitationalAnomaly |
P60054
|
FINISHED |
| Object | mascon |
—
|
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: mascon | Statement: [Mare Tranquillitatis, hasGravitationalAnomaly, mascon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGravitationalAnomaly Context triple: [Mare Tranquillitatis, hasGravitationalAnomaly, mascon]
-
A.
surfaceGravityAnomaly
chosen
Indicates a deviation of an object's local surface gravitational acceleration from a reference or expected gravitational field.
-
B.
hasSatelliteCrater
Indicates that one crater is a secondary or subsidiary crater associated with, and typically located near, another primary crater.
-
C.
geographicalAnomaly
Indicates a relationship where a location exhibits unusual or irregular geographical features or conditions compared to its surrounding area.
-
D.
interactsGravitationallyWith
Indicates that one entity exerts a gravitational influence on, and is influenced by, another entity, according to the laws of gravity.
-
E.
hasCrater
Indicates that one entity possesses or features a crater on its surface.
- 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_69c00876a69881908088a2626d3b2666 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056e108fc81908775d176ff960fad |
completed | March 22, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69c049eb52a08190ac10fd703735f5aa |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:08 p.m.