Triple
T32599896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shorty crater |
E833335
|
entity |
| Predicate | hasApolloSiteDesignation |
P192388
|
FINISHED |
| Object | Apollo 17 Station 4 region |
—
|
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: Apollo 17 Station 4 region | Statement: [Shorty crater, hasApolloSiteDesignation, Apollo 17 Station 4 region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApolloSiteDesignation Context triple: [Shorty crater, hasApolloSiteDesignation, Apollo 17 Station 4 region]
-
A.
hasDiscoveryDesignation
Indicates that an entity has been assigned a specific designation or label associated with its discovery.
-
B.
hasPleiadesDesignation
Indicates that an astronomical object is assigned a specific designation within the Pleiades star cluster catalog.
-
C.
hasIAUName
Indicates that an entity is assigned an official name as recognized by the International Astronomical Union (IAU).
-
D.
hasMainLandingSite
Indicates that an entity has a primary or principal location where it arrives, lands, or makes contact.
-
E.
NASADesignation
Indicates that an entity has been assigned an official identification or catalog number by NASA.
- 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_69f3492ab63c8190aec24d5003b47c29 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69fd098357348190a835c0b6d99857d2 |
completed | May 7, 2026, 9:52 p.m. |
Created at: May 1, 2026, 1:05 a.m.