Triple
T5637007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beta Crucis |
E147971
|
entity |
| Predicate | hasAngularSeparationFromA_C |
P60658
|
FINISHED |
| Object | about 30 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 30 arcseconds | Statement: [Beta Crucis, hasAngularSeparationFromA_C, about 30 arcseconds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAngularSeparationFromA_C Context triple: [Beta Crucis, hasAngularSeparationFromA_C, about 30 arcseconds]
-
A.
angularSeparationFrom
chosen
Indicates the angular distance between two entities as measured from a common observation point.
-
B.
angularSeparationBetweenComplexes
Indicates the angular distance or orientation difference measured between two complexes.
-
C.
hasAphelionNear
Indicates that one celestial body's aphelion (its farthest point from the object it orbits) lies close to another specified reference point or object.
-
D.
isAsterismOf
Indicates that one or more stars collectively form or belong to a specific asterism.
-
E.
hasCloseApproachGeometry
Indicates that there exists detailed geometric information describing the spatial configuration and trajectory of a close approach event between two entities.
- 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_69c00907bc8881909ed760d3ed73ef35 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c022809f708190ab859aa446683b10 |
completed | March 22, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69c01b1f12ec8190b4b9d9ee31cabe19 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:41 p.m.