Triple
T6175055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beta Cancri |
E137796
|
entity |
| Predicate | variableStarStatus |
P64734
|
FINISHED |
| Object | not known to be variable |
—
|
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: not known to be variable | Statement: [Beta Cancri, variableStarStatus, not known to be variable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: variableStarStatus Context triple: [Beta Cancri, variableStarStatus, not known to be variable]
-
A.
isVariableStar
chosen
Indicates that an astronomical object exhibits intrinsic brightness variations over time, classifying it as a variable star.
-
B.
variableStarType
Indicates the specific classification of variability that characterizes a variable star’s changing brightness.
-
C.
hasVariableStarDesignation
Indicates that an entity is assigned a specific variable star designation in an astronomical naming system.
-
D.
starType
Indicates the classification relationship specifying what type or category of star an astronomical object is.
-
E.
cataloguedAsStar
Indicates that an object has been classified and recorded specifically as a star in a catalog or database.
- 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_69c008a80f748190ba3d07ffc81acb29 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05dc55b5c819084482b735771c9a8 |
completed | March 22, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c055f7f12881908e21c04e9b752ba4 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:18 p.m.