Triple
T14160678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schwarzschild M |
E350930
|
entity |
| Predicate | hasSatelliteCraterDesignation |
P50433
|
FINISHED |
| Object | M |
—
|
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: M | Statement: [Schwarzschild M, hasSatelliteCraterDesignation, M]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSatelliteCraterDesignation Context triple: [Schwarzschild M, hasSatelliteCraterDesignation, M]
-
A.
hasSatelliteCrater
Indicates that one crater is a secondary or subsidiary crater associated with, and typically located near, another primary crater.
-
B.
notableCrater
Indicates that a crater is especially prominent, significant, or well-known in relation to a particular celestial body or context.
-
C.
hasCraterNamedAfter
Indicates that a crater is named in honor of a particular person, place, or entity.
-
D.
satelliteCraterNamingConvention
chosen
Indicates the naming rule by which smaller satellite craters are designated in relation to a primary, named crater.
-
E.
craterName
Indicates that one entity is the designated name assigned to a specific crater.
- 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61393f308190bb357e2bd1916f94 |
completed | April 14, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:59 a.m.