Triple
T33829950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 169P/NEAT |
E867067
|
entity |
| Predicate | hasCometDesignation |
P206688
|
FINISHED |
| Object | 169P/NEAT |
E867067
|
NE 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: 169P/NEAT | Statement: [169P/NEAT, hasCometDesignation, 169P/NEAT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCometDesignation Context triple: [169P/NEAT, hasCometDesignation, 169P/NEAT]
-
A.
hasNameInCometDesignation
Indicates that an entity’s name appears as part of its official comet designation.
-
B.
isCometOf
Indicates that one entity is a comet that belongs to, or is associated with, another entity (such as a star system, galaxy, or celestial body).
-
C.
hasComet-likeOrbit
Indicates that an object's orbit shares key dynamical characteristics with those of comets, such as high eccentricity, inclination, or origin in cometary populations.
-
D.
hasMinorPlanetCenterDesignation
Indicates that an entity is assigned an official designation by the Minor Planet Center (e.g., for asteroids or other small Solar System bodies).
-
E.
hasFK5Designation
Indicates that an entity is associated with a specific FK5 (Fifth Fundamental Catalogue) astronomical designation.
- F. None of above. chosen
Provenance (5 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_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a366ea6d0e08190ae46c6202d4129a0 |
completed | June 20, 2026, 10:42 a.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037e07fe4481909ca21eae7a941ee7 |
completed | May 12, 2026, 7:22 p.m. |
Created at: May 1, 2026, 1:46 a.m.