Triple
T19261112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caelum |
E481650
|
entity |
| Predicate | hasBrightStarBrighterThanMagnitude2 |
P23774
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Caelum, hasBrightStarBrighterThanMagnitude2, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBrightStarBrighterThanMagnitude2 Context triple: [Caelum, hasBrightStarBrighterThanMagnitude2, false]
-
A.
hasNoStarBrighterThanMagnitude
Indicates that, within a given set or system, there is no star whose brightness exceeds (is numerically less than) the specified magnitude threshold.
-
B.
hasSecondBrightestStar
Indicates that one entity possesses or is associated with another entity that is the second most luminous star within a specified group or system.
-
C.
hasBrightStarDesignation
Indicates that an entity is assigned a specific identifier in the Bright Star Catalogue.
-
D.
isBrightStar
Indicates that the subject star has a high intrinsic luminosity or apparent brightness compared to typical stars.
-
E.
hasBrightStar
chosen
Indicates that one entity possesses, contains, or is associated with a star characterized by high brightness.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb890e7c8190beba407f63459382 |
completed | April 20, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:28 p.m.