Triple
T6042797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mare Tranquillitatis |
E134588
|
entity |
| Predicate | hasSelenographicLatitude |
P37333
|
FINISHED |
| Object | 8.5° N |
—
|
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: 8.5° N | Statement: [Mare Tranquillitatis, hasSelenographicLatitude, 8.5° N]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSelenographicLatitude Context triple: [Mare Tranquillitatis, hasSelenographicLatitude, 8.5° N]
-
A.
selenographicLongitude
Indicates the longitudinal position of a point on the Moon’s surface measured east or west from the Moon’s prime meridian.
-
B.
lunarLatitude
chosen
Indicates the angular distance of a point on the Moon north or south of the lunar equator.
-
C.
lunarLongitude
Indicates the angular position of the Moon along its orbital path, measured as longitude relative to a defined reference direction or point.
-
D.
hasPlanetographicLatitudeDirection
Indicates that something possesses or is associated with a specific directional component (e.g., north or south) of its planetographic latitude.
-
E.
isBestSeenFromLatitudes
Indicates that something is most optimally or clearly observable when viewed from specific geographic latitudes.
- 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.