Triple
T19752502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sigma Sagittarii |
E474414
|
entity |
| Predicate | companionSeparation_arcsec |
P69289
|
FINISHED |
| Object | ~5.2 |
—
|
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: ~5.2 | Statement: [Sigma Sagittarii, companionSeparation_arcsec, ~5.2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: companionSeparation_arcsec Context triple: [Sigma Sagittarii, companionSeparation_arcsec, ~5.2]
-
A.
hasCompanionSeparation_arcsec
chosen
Indicates the angular separation, measured in arcseconds, between an object and its companion.
-
B.
hasOpticalCompanion
Indicates that one entity has another entity as an associated optical companion, typically observed as a nearby or paired object in optical wavelengths.
-
C.
hasCompanionStar
Indicates that an astronomical object is gravitationally bound to and forms a system with another star.
-
D.
hasCompanionMagnitude
Indicates that one entity is associated with another entity whose magnitude (such as size, intensity, or value) is being specified or characterized.
-
E.
angularSeparationFrom
Indicates the angular distance between two entities as measured from a common observation point.
- 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_69d8e51940a0819087bd2996f98da668 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6529bcb8c8190bcca61a53be86757 |
completed | April 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:48 p.m.