Triple
T33829726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HR 8278 |
E867062
|
entity |
| Predicate | visibleFromNorthernHemisphere |
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: [HR 8278, visibleFromNorthernHemisphere, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visibleFromNorthernHemisphere Context triple: [HR 8278, visibleFromNorthernHemisphere, true]
-
A.
visibleInHemisphere
Indicates that an object or phenomenon can be seen or observed from a specified hemisphere of a celestial body.
-
B.
visibleFromEarth
Indicates that the object can be observed from Earth, either with the naked eye or with appropriate instruments, under suitable viewing conditions.
-
C.
isInNorthernCelestialHemisphere
chosen
Indicates that an astronomical object’s position lies north of the celestial equator in the northern half of the sky.
-
D.
visibleFromLatitudeNorth
Indicates that something can be seen or observed from locations at or north of a specified latitude.
-
E.
isCircumpolarFromSouthernLatitudes
Indicates that an object remains continuously above the horizon and never sets when observed from southern latitudes.
- 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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:46 a.m.