Triple
T23244296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hipparcos Catalogue |
E581539
|
entity |
| Predicate | includesBrightStars |
P23774
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Hipparcos Catalogue, includesBrightStars, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesBrightStars Context triple: [Hipparcos Catalogue, includesBrightStars, yes]
-
A.
hasBrightStar
chosen
Indicates that one entity possesses, contains, or is associated with a star characterized by high brightness.
-
B.
isBrightStar
Indicates that the subject star has a high intrinsic luminosity or apparent brightness compared to typical stars.
-
C.
containsBrightStarsBrighterThanMagnitude4
Indicates that the subject region or object includes at least one bright star whose apparent magnitude is numerically less than 4 (i.e., brighter than magnitude 4).
-
D.
hasBrightStarDesignation
Indicates that an entity is assigned a specific identifier in the Bright Star Catalogue.
-
E.
starIs
Indicates that one entity is identified or classified as a star in relation to another entity or context.
- 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_69e24606b17c81908aba1a4911c8a8ba |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f193ee37c8819091f799506fa532da |
completed | April 29, 2026, 5:15 a.m. |
| PD | Predicate disambiguation | batch_69effcdadec0819092ec1749ee453b4e |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:10 p.m.