Triple
T34975928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fermi |
E1008675
|
entity |
| Predicate | hasOverlappingCrater |
P182159
|
FINISHED |
| Object | Tsiolkovskiy (on southwest rim vicinity) |
—
|
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: Tsiolkovskiy (on southwest rim vicinity) | Statement: [Fermi, hasOverlappingCrater, Tsiolkovskiy (on southwest rim vicinity)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOverlappingCrater Context triple: [Fermi, hasOverlappingCrater, Tsiolkovskiy (on southwest rim vicinity)]
-
A.
hasSatelliteCrater
Indicates that one crater is a secondary or subsidiary crater associated with, and typically located near, another primary crater.
-
B.
hasCrater
Indicates that one entity possesses or features a crater on its surface.
-
C.
hasMultipleCraters
Indicates that an entity possesses or is characterized by more than one crater.
-
D.
hasCraterType
Indicates that an object or location is associated with a specific type or classification of crater.
-
E.
hasCraterCount
Indicates that an entity possesses a specified number of craters.
- 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_69f76dc78a308190a1ac29ad4a9a4895 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7870dfe108190996c0c68630edc7f |
completed | May 3, 2026, 5:34 p.m. |
Created at: May 3, 2026, 4:01 p.m.