Triple
T33900012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | α Aquarii |
E869019
|
entity |
| Predicate | isProminentNavigationStar |
P63030
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [α Aquarii, isProminentNavigationStar, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isProminentNavigationStar Context triple: [α Aquarii, isProminentNavigationStar, true]
-
A.
isNavigationStar
chosen
Indicates that one entity serves as a guiding or reference star used for navigation relative to another entity.
-
B.
isBrightStar
Indicates that the subject star has a high intrinsic luminosity or apparent brightness compared to typical stars.
-
C.
isGiantStar
Indicates that a star has an exceptionally large radius and luminosity compared to main-sequence stars, classifying it as a giant star.
-
D.
isGuideStarFor
Indicates that one celestial object serves as a reference or calibration star used to guide or stabilize the observation or pointing of another object or instrument.
-
E.
isStandardStar
Indicates that an astronomical object is classified as a normal, main-sequence or otherwise typical star, rather than an exotic or non-standard stellar object.
- 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_69f34997703c8190866b1d404bce531f |
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:48 a.m.