Triple
T33830012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crater |
E867069
|
entity |
| Predicate | hasIAUThreeLetterAbbreviation |
P135118
|
FINISHED |
| Object | Crt |
—
|
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: Crt | Statement: [Crater, hasIAUThreeLetterAbbreviation, Crt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIAUThreeLetterAbbreviation Context triple: [Crater, hasIAUThreeLetterAbbreviation, Crt]
-
A.
hasThreeLetterIAUCode
chosen
Indicates that an entity is associated with a specific three-letter code defined by the International Astronomical Union (IAU).
-
B.
hasIAUName
Indicates that an entity is assigned an official name as recognized by the International Astronomical Union (IAU).
-
C.
hasThreeLetterForm
Indicates that an entity’s written or symbolic form consists of exactly three letters.
-
D.
hasNameAbbreviation
Indicates that an entity is associated with a shortened or abbreviated form of its full name.
-
E.
hasISO3166Alpha3Code
Indicates that an entity is associated with a specific three-letter country code defined by the ISO 3166-1 alpha-3 standard.
- 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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:46 a.m.