Triple
T3615063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kepler (lunar crater) |
E76579
|
entity |
| Predicate | locatedInMare |
P40
|
FINISHED |
| Object | border region of Oceanus Procellarum |
—
|
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: border region of Oceanus Procellarum | Statement: [Kepler (lunar crater), locatedInMare, border region of Oceanus Procellarum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInMare Context triple: [Kepler (lunar crater), locatedInMare, border region of Oceanus Procellarum]
-
A.
locatedOnSideOfMoon
Indicates that one entity is situated on a specific side or hemisphere of the Moon relative to another reference frame or viewpoint.
-
B.
lunarLandingRegion
Indicates the geographic region on the Moon where a spacecraft or mission has landed.
-
C.
hasSatelliteCrater
Indicates that one crater is a secondary or subsidiary crater associated with, and typically located near, another primary crater.
-
D.
locatedInSkyRegion
Indicates that an entity is situated within or associated with a specific region or area of the sky.
-
E.
locatedIn
chosen
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
- 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_69ad85da0ba481908b3b48c69efe2b98 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc27b5e008190a72a8dab7d736e64 |
completed | March 8, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69adb83f1e4c8190ab501c1c05b14c08 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.