Triple
T24547206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HR 4763 |
E607257
|
entity |
| Predicate | isSouthernHemisphereObject |
P140764
|
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 4763, isSouthernHemisphereObject, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSouthernHemisphereObject Context triple: [HR 4763, isSouthernHemisphereObject, true]
-
A.
isSouthernHemisphereTimeZone
Indicates that a time zone is located in, or primarily associated with, the Southern Hemisphere.
-
B.
isLocatedInSouthernCelestialHemisphere
chosen
Indicates that the referenced celestial object or region lies in the southern half of the celestial sphere, south of the celestial equator.
-
C.
isOnSouthernPartOf
Indicates that one entity is located on the southern part or southern region of another entity.
-
D.
isInNorthernCelestialHemisphere
Indicates that an astronomical object’s position lies north of the celestial equator in the northern half of the sky.
-
E.
containsSouthCelestialPole
Indicates that a celestial region or frame includes the location of the South Celestial Pole within its boundaries.
- 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_69e2c4c9bf94819082d05da6f5c29907 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8caba8c819082c3bf33b6ff9cd0 |
completed | April 30, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:27 a.m.