Triple
T32769106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Levi-Civita D |
E837985
|
entity |
| Predicate | hasParentCraterDesignation |
P198999
|
FINISHED |
| Object | Levi-Civita |
—
|
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: Levi-Civita | Statement: [Levi-Civita D, hasParentCraterDesignation, Levi-Civita]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentCraterDesignation Context triple: [Levi-Civita D, hasParentCraterDesignation, Levi-Civita]
-
A.
parentCrater
Indicates that one crater is the source or origin from which another crater was formed or derived.
-
B.
hasEponymParentCrater
Indicates that a crater is named after, or derives its name from, another crater that serves as its eponymous parent.
-
C.
isSecondaryCraterOf
Indicates that one crater was formed by ejecta from the impact that created another, primary crater, rather than by a direct impact itself.
-
D.
hasOverlappingCrater
Indicates that one crater partially or fully overlaps another crater in space, sharing a common area of their surfaces.
-
E.
isNamedCraterOn
Indicates that a crater bears a specific name and is located on a particular celestial body.
- 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_69f34939857c8190aa9970c51feec1eb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff1a972bf08190860696ffcd887c0f |
completed | May 9, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69ff184005d88190bf38283ebc499b28 |
completed | May 9, 2026, 11:19 a.m. |
| PDg | Predicate description generation | batch_69ff1a95b6fc81909331bb03e263b5b9 |
completed | May 9, 2026, 11:29 a.m. |
Created at: May 1, 2026, 1:13 a.m.