Triple
T36724792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubble D |
E907163
|
entity |
| Predicate | IUGSPlanetaryNomenclatureStatus |
P71313
|
FINISHED |
| Object | approved lunar feature name |
—
|
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: approved lunar feature name | Statement: [Hubble D, IUGSPlanetaryNomenclatureStatus, approved lunar feature name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IUGSPlanetaryNomenclatureStatus Context triple: [Hubble D, IUGSPlanetaryNomenclatureStatus, approved lunar feature name]
-
A.
hasIAUName
Indicates that an entity is assigned an official name as recognized by the International Astronomical Union (IAU).
-
B.
planetDesignation
Indicates the formal naming or labeling assigned to a planet within a particular cataloging or classification system.
-
C.
IAUNameApproval
Indicates that an official name for an astronomical object or feature has been formally approved by the International Astronomical Union (IAU).
-
D.
isNonOfficialIAU
Indicates that the entity’s designation or status is not officially recognized or approved by the International Astronomical Union (IAU).
-
E.
toponymStatus
chosen
Indicates the status or classification of a place name within a geographic naming or toponymic system.
- 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_69f76e746e4c8190a0d05cc6d57a643e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.