Triple
T23527610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Algieba |
E576475
|
entity |
| Predicate | hasAngularSeparation |
P60658
|
FINISHED |
| Object | about 4.4 arcseconds |
—
|
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.4 arcseconds | Statement: [Algieba, hasAngularSeparation, about 4.4 arcseconds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAngularSeparation Context triple: [Algieba, hasAngularSeparation, about 4.4 arcseconds]
-
A.
angularSeparationFrom
chosen
Indicates the angular distance between two entities as measured from a common observation point.
-
B.
hasAngularSeparationFromNorthCelestialPole
Indicates the angular distance between an object’s position in the sky and the north celestial pole.
-
C.
angularSeparationBetweenComplexes
Indicates the angular distance or orientation difference measured between two complexes.
-
D.
angularSeparationFromMilkyWayCenter
Indicates the angular distance between an object’s position in the sky and the direction of the Milky Way’s center.
-
E.
hasApproximateAngularSize
Indicates that one entity has an angular size, as seen from another entity or reference point, that is approximately equal to a specified value.
- 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_69e245f5a8848190a2ba42e271c6c31f |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ac74be1881909161b94aa611188a |
completed | April 29, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:09 p.m.