Triple
T24304931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAO 251145 |
E612506
|
entity |
| Predicate | angularSeparationFromGacrux_deg |
P155489
|
FINISHED |
| Object | about 4 |
—
|
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: about 4 | Statement: [SAO 251145, angularSeparationFromGacrux_deg, about 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: angularSeparationFromGacrux_deg Context triple: [SAO 251145, angularSeparationFromGacrux_deg, about 4]
-
A.
angularSeparationFrom
Indicates the angular distance between two entities as measured from a common observation point.
-
B.
angularSeparationFromMilkyWayCenter
Indicates the angular distance between an object’s position in the sky and the direction of the Milky Way’s center.
-
C.
hasAngularSeparationFromNorthCelestialPole
Indicates the angular distance between an object’s position in the sky and the north celestial pole.
-
D.
separationFromPollux_deg
Indicates the angular separation, measured in degrees, between an object and the star Pollux.
-
E.
angularSeparationBetweenComplexes
Indicates the angular distance or orientation difference measured between two complexes.
- 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_69e2d7d91bb48190bc5377d17a85fb21 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2922641bc81908fa3595941e60741 |
completed | April 29, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
| PDg | Predicate description generation | batch_69f1c6d4e99081909f61899eccafb73e |
completed | April 29, 2026, 8:52 a.m. |
Created at: April 18, 2026, 1:30 a.m.