Triple
T26300536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saturn XIII |
E661541
|
entity |
| Predicate | hasIAUNumbering |
P37553
|
FINISHED |
| Object | Saturn XIII |
—
|
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: Saturn XIII | Statement: [Saturn XIII, hasIAUNumbering, Saturn XIII]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIAUNumbering Context triple: [Saturn XIII, hasIAUNumbering, Saturn XIII]
-
A.
hasScientificDesignation
Indicates that an entity is associated with a specific formal scientific name or designation used in scientific classification or nomenclature.
-
B.
UNSNumber
Indicates that an entity is associated with a specific United Nations (UN) number used to identify hazardous substances or dangerous goods.
-
C.
IUCNStatusSystem
Indicates the conservation status classification framework used to assign an IUCN threat category to a species or taxon.
-
D.
isNumberedBy
chosen
Indicates that an entity is assigned, identified, or organized by a specific number or numbering scheme.
-
E.
hasIAUName
Indicates that an entity is assigned an official name as recognized by the International Astronomical Union (IAU).
- 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60eb1ac9c8190a0b9193f4108dfbe |
completed | May 2, 2026, 2:48 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:15 p.m.