Triple
T21720280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beta Geminorum |
E536135
|
entity |
| Predicate | isNorthernHemisphereStar |
P65285
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Beta Geminorum, isNorthernHemisphereStar, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNorthernHemisphereStar Context triple: [Beta Geminorum, isNorthernHemisphereStar, true]
-
A.
isInNorthernCelestialHemisphere
chosen
Indicates that an astronomical object’s position lies north of the celestial equator in the northern half of the sky.
-
B.
isCircumpolarFromSouthernLatitudes
Indicates that an object remains continuously above the horizon and never sets when observed from southern latitudes.
-
C.
isCircumpolar
Indicates that an astronomical object remains perpetually above the horizon from a given observation point, never setting below it.
-
D.
isLocatedInSouthernCelestialHemisphere
Indicates that the referenced celestial object or region lies in the southern half of the celestial sphere, south of the celestial equator.
-
E.
locatedInNorthernHemisphere
Indicates that the subject is geographically situated in the Northern Hemisphere of the Earth.
- 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_69e0c46c6dd88190a595375fa6ebd701 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efd96de818819084c268d4775a8e3a |
completed | April 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:47 p.m.