Triple
T23199730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bet Cnc |
E579972
|
entity |
| Predicate | angularSeparationFromCompanionArcseconds |
P69289
|
FINISHED |
| Object | about 29 |
—
|
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 29 | Statement: [Bet Cnc, angularSeparationFromCompanionArcseconds, about 29]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: angularSeparationFromCompanionArcseconds Context triple: [Bet Cnc, angularSeparationFromCompanionArcseconds, about 29]
-
A.
hasCompanionSeparation_arcsec
chosen
Indicates the angular separation, measured in arcseconds, between an object and its companion.
-
B.
angularSeparationFrom
Indicates the angular distance between two entities as measured from a common observation point.
-
C.
angularSeparationBetweenComplexes
Indicates the angular distance or orientation difference measured between two complexes.
-
D.
separationFromPollux_deg
Indicates the angular separation, measured in degrees, between an object and the star Pollux.
-
E.
opticalCompanionMass
Indicates the mass of a companion object as determined from optical observations or measurements.
- 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_69e24600eed08190bd7e5295653a1503 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1907835448190aa4fc234d15527c3 |
completed | April 29, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:06 p.m.