Triple
T6642739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delta Crucis |
E150625
|
entity |
| Predicate | isBrightestRankInCrux |
P71885
|
FINISHED |
| Object | third-brightest star in Crux |
—
|
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: third-brightest star in Crux | Statement: [Delta Crucis, isBrightestRankInCrux, third-brightest star in Crux]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBrightestRankInCrux Context triple: [Delta Crucis, isBrightestRankInCrux, third-brightest star in Crux]
-
A.
brightestStar
Indicates that one entity is the most luminous star within a specified group, region, or context relative to the others.
-
B.
isBrightestOpenClusterIn
Indicates that one open star cluster is the most luminous (brightest) among all open clusters within a specified region or context.
-
C.
isBrightStar
Indicates that the subject star has a high intrinsic luminosity or apparent brightness compared to typical stars.
-
D.
isBrightestKTypeGiantVisible
Indicates that the entity is the brightest visible star among those classified as K-type giant stars.
-
E.
hasBrightStar
Indicates that one entity possesses, contains, or is associated with a star characterized by high brightness.
- F. None of above. chosen
Provenance (4 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_69c687f1a3048190828b7342f7125d5c |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6c308a08881908501c862b3029321 |
completed | March 27, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c6ad024860819084b9b535b136ede6 |
completed | March 27, 2026, 4:14 p.m. |
| PDg | Predicate description generation | batch_69c6c30733908190980f7ffaa5c5527b |
completed | March 27, 2026, 5:48 p.m. |
Created at: March 27, 2026, 2 p.m.