Triple
T30874083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chaffee (lunar crater) |
E786425
|
entity |
| Predicate | officialNameAdoptedByIAU |
P50431
|
FINISHED |
| Object | 1970 |
—
|
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: 1970 | Statement: [Chaffee (lunar crater), officialNameAdoptedByIAU, 1970]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialNameAdoptedByIAU Context triple: [Chaffee (lunar crater), officialNameAdoptedByIAU, 1970]
-
A.
IAUNameApproval
chosen
Indicates that an official name for an astronomical object or feature has been formally approved by the International Astronomical Union (IAU).
-
B.
isNonOfficialIAU
Indicates that the entity’s designation or status is not officially recognized or approved by the International Astronomical Union (IAU).
-
C.
hasIAUName
Indicates that an entity is assigned an official name as recognized by the International Astronomical Union (IAU).
-
D.
officialNameGivenBy
Indicates that an official or formal name has been assigned to an entity by a specific authority or source.
-
E.
officialName
Indicates the formally recognized name assigned to an entity by an authoritative body or source.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe9b0276d48190b554fa22b043e6d8 |
completed | May 9, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69fe999692b081909921e1148d66f0ef |
completed | May 9, 2026, 2:19 a.m. |
Created at: April 29, 2026, 8:48 p.m.