Triple
T33525092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyerly |
E858615
|
entity |
| Predicate | hasClimateHemisphere |
P177765
|
FINISHED |
| Object | Northern Hemisphere |
—
|
NE NERFINISHED |
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: Northern Hemisphere | Statement: [Lyerly, hasClimateHemisphere, Northern Hemisphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClimateHemisphere Context triple: [Lyerly, hasClimateHemisphere, Northern Hemisphere]
-
A.
hemisphereName
Indicates the named hemisphere (e.g., northern, southern, eastern, or western) that a given location or entity belongs to.
-
B.
liesInHemisphere
chosen
Indicates that one geographic entity is located within a specified hemisphere of the Earth.
-
C.
hasProgenyInHemisphere
Indicates that an entity has offspring or descendants located within a specified hemisphere.
-
D.
hemispherePresence
Indicates the spatial relationship of whether and in which hemisphere(s) (e.g., northern, southern, eastern, western) an entity is present or occurs.
-
E.
hasClimate
Indicates that an entity possesses or is characterized by a particular type of climate or climatic conditions.
- 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_69f349781c6c819082c516b260efe7e2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: May 1, 2026, 1:39 a.m.