Triple
T34324468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HIP 105515 |
E880827
|
entity |
| Predicate | hasAngularSeparationBetweenMainComponents |
P69289
|
FINISHED |
| Object | about 3.5 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 3.5 arcseconds | Statement: [HIP 105515, hasAngularSeparationBetweenMainComponents, about 3.5 arcseconds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAngularSeparationBetweenMainComponents Context triple: [HIP 105515, hasAngularSeparationBetweenMainComponents, about 3.5 arcseconds]
-
A.
angularSeparationFrom
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.
hasCompanionSeparation_arcsec
chosen
Indicates the angular separation, measured in arcseconds, between an object and its companion.
-
D.
hasAngularSeparationFromNorthCelestialPole
Indicates the angular distance between an object’s position in the sky and the north celestial pole.
-
E.
hasCompanionSeparation
Indicates that one entity is separated or kept apart from its companion or associated counterpart.
- 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_69f349b9cd508190a996a616903b3e6d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: May 1, 2026, 1:58 a.m.