Triple
T22936141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mare Fecunditatis |
E569588
|
entity |
| Predicate | neighboringMare |
P150319
|
FINISHED |
| Object | Mare Tranquillitatis |
—
|
NE NERFINISHED |
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: Mare Tranquillitatis | Statement: [Mare Fecunditatis, neighboringMare, Mare Tranquillitatis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neighboringMare Context triple: [Mare Fecunditatis, neighboringMare, Mare Tranquillitatis]
-
A.
neighboringMoon
Indicates that one moon or natural satellite is directly adjacent to or in close orbital proximity to another moon around the same or nearby celestial body.
-
B.
lunarMareAssociation
Indicates an association or relationship between something and a lunar mare (a dark, basaltic plain on the Moon).
-
C.
neighboringMoons
Indicates that two moons orbiting the same or nearby celestial bodies are close enough in space to be considered neighbors.
-
D.
isOnLargerMoonOf
Indicates that one entity is located on a moon that is larger than another referenced moon.
-
E.
neighboringCrater
Indicates that one crater is located adjacent to or very close to another crater, such that they are considered neighbors on a surface.
- F. None of above. chosen
Provenance (4 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_69e24590862c8190858f180ad302adab |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1813608e48190922df7a5386dc391 |
completed | April 29, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:44 p.m.