Triple
T32366813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amundsen crater |
E827015
|
entity |
| Predicate | hasOfficialNameStatus |
P180661
|
FINISHED |
| Object | approved by IAU |
—
|
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 by IAU | Statement: [Amundsen crater, hasOfficialNameStatus, approved by IAU]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialNameStatus Context triple: [Amundsen crater, hasOfficialNameStatus, approved by IAU]
-
A.
hasOfficialNameContaining
Indicates that an entity’s official name includes a specified substring or sequence of characters.
-
B.
hasOfficialUNName
Indicates that an entity possesses an official name as formally recognized by the United Nations.
-
C.
hasOfficialNameVariant
Indicates that an entity has an alternative official form or version of its name.
-
D.
hasOfficialDualNameWith
Indicates that two entities share an officially recognized dual or joint name used in formal contexts.
-
E.
hasOfficialNameInEnglish
Indicates that an entity has an officially recognized name expressed in the English language.
- 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_69f349166d548190887b412fe908e2f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f74654c09c819084879162eba9d641 |
completed | May 3, 2026, 12:57 p.m. |
Created at: May 1, 2026, 12:50 a.m.