Triple
T28249062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gliese 244 |
E712265
|
entity |
| Predicate | brightestStarIn |
P6956
|
FINISHED |
| Object | night sky |
—
|
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: night sky | Statement: [Gliese 244, brightestStarIn, night sky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brightestStarIn Context triple: [Gliese 244, brightestStarIn, night sky]
-
A.
brightestStar
chosen
Indicates that one entity is the most luminous star within a specified group, region, or context relative to the others.
-
B.
brightestStarApparentMagnitude
Indicates the apparent brightness value (magnitude) of the brightest star as seen from a given observation point.
-
C.
brightestStarAlternativeName
Indicates that an alternative or secondary name is used to refer to the same brightest star in a given context or system.
-
D.
isBrightestStarOfTypeIn
Indicates that a star is the most luminous (brightest) member among all stars of a given type within a specified region or group.
-
E.
brightestStarTraditionalName
Indicates that the object is the brightest star in a given context and provides its traditional (historical or culturally established) name.
- 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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f643ee1a1881909a7f4588daba8eca |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 11:03 p.m.