Triple
T21884492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HR 1852 |
E540369
|
entity |
| Predicate | isNearCelestialEquator |
P146044
|
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 1852, isNearCelestialEquator, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNearCelestialEquator Context triple: [HR 1852, isNearCelestialEquator, true]
-
A.
hasApproximateDistanceFromEquator
Indicates that one entity has an approximate measured or estimated distance from the Earth's equator.
-
B.
liesOnEcliptic
Indicates that the referenced object’s position is located on or very close to the plane of the ecliptic.
-
C.
hasEclipticProximity
Indicates that one celestial object lies close to another in terms of angular separation along or near the ecliptic plane.
-
D.
isCircumpolar
Indicates that an astronomical object remains perpetually above the horizon from a given observation point, never setting below it.
-
E.
isInNorthernCelestialHemisphere
Indicates that an astronomical object’s position lies north of the celestial equator in the northern half of the sky.
- F. None of above. chosen
Provenance (4 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_69e0c479a98081908ce333853fdd4348 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f118eabb008190ab6f1364ef4e6feb |
completed | April 28, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e6be9a65888190a66598d62d20366c |
completed | April 21, 2026, 12:02 a.m. |
| PDg | Predicate description generation | batch_69e6d054737081908aa7112975b77475 |
completed | April 21, 2026, 1:18 a.m. |
Created at: April 16, 2026, 7:05 p.m.