Triple
T19261271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uranometria |
E481653
|
entity |
| Predicate | usesStarDesignationSystem |
P135121
|
FINISHED |
| Object | Bayer designation |
—
|
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: Bayer designation | Statement: [Uranometria, usesStarDesignationSystem, Bayer designation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesStarDesignationSystem Context triple: [Uranometria, usesStarDesignationSystem, Bayer designation]
-
A.
hasBrightStarDesignation
Indicates that an entity is assigned a specific identifier in the Bright Star Catalogue.
-
B.
hasVariableStarDesignation
Indicates that an entity is assigned a specific variable star designation in an astronomical naming system.
-
C.
usesConstellation
Indicates that one entity makes use of, relies on, or incorporates a particular constellation in its function, representation, or operation.
-
D.
isAsterismOf
Indicates that one or more stars collectively form or belong to a specific asterism.
-
E.
missionDesignationSystem
Indicates a system that assigns or manages official designations or identifiers for missions.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb8a022c8190b313e9d11d38e482 |
completed | April 20, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4ddcf50108190a09d0f1291c17374 |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 1:28 p.m.