Triple
T11285970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burnwell, Alabama |
E267186
|
entity |
| Predicate | isInNorthHemisphere |
P26575
|
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: [Burnwell, Alabama, isInNorthHemisphere, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInNorthHemisphere Context triple: [Burnwell, Alabama, isInNorthHemisphere, true]
-
A.
isInNorthernCelestialHemisphere
Indicates that an astronomical object’s position lies north of the celestial equator in the northern half of the sky.
-
B.
locatedInNorthernHemisphere
Indicates that the subject is geographically situated in the Northern Hemisphere of the Earth.
-
C.
locatedInTheNorthernHemisphere
chosen
Indicates that the subject entity is situated geographically within the northern half of the Earth, above the equator.
-
D.
isNorthernmost
Indicates that one entity is located farther north than all other comparable entities in a given set or region.
-
E.
directionInNorthernHemisphere
Indicates that the specified direction is defined or measured relative to the orientation of the Northern Hemisphere (e.g., based on its geographic or celestial reference frame).
- 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_69d6aac993a08190a6f36445ebaf9a43 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e986b0f08190a414749eaa7f1a5d |
completed | April 9, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69d787a240588190aa097298f951c915 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:31 p.m.