Triple
T30022285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sikorsky W |
E762778
|
entity |
| Predicate | associatedMainCrater |
P95999
|
FINISHED |
| Object | Sikorsky (crater) |
E1878928
|
NE 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: Sikorsky (crater) | Statement: [Sikorsky W, associatedMainCrater, Sikorsky (crater)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedMainCrater Context triple: [Sikorsky W, associatedMainCrater, Sikorsky (crater)]
-
A.
isSecondaryCraterOf
Indicates that one crater was formed by ejecta from the impact that created another, primary crater, rather than by a direct impact itself.
-
B.
dominantCraterName
Indicates that one crater is identified as the primary or most prominent (dominant) crater associated with another feature or context.
-
C.
mainCrater
chosen
Indicates that one crater is the primary or most significant crater associated with another crater or crater-related feature.
-
D.
largestCraterName
Indicates the name of the largest crater associated with a given celestial body or region.
-
E.
notableCrater
Indicates that a crater is especially prominent, significant, or well-known in relation to a particular celestial body or context.
- F. None of above.
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_69f2246ee6e48190b69e837b913b398a |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a276ed954488190b3f6f3fbbf0b6db3 |
completed | June 9, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 6:47 p.m.