Triple
T18809576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Kling |
E459971
|
entity |
| Predicate | isInLatitudeZone |
P13005
|
FINISHED |
| Object | sub-Antarctic |
—
|
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: sub-Antarctic | Statement: [Mount Kling, isInLatitudeZone, sub-Antarctic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInLatitudeZone Context triple: [Mount Kling, isInLatitudeZone, sub-Antarctic]
-
A.
liesWithinLatitudeBand
chosen
Indicates that one geographic entity is located within a specified range of latitudes defined as a latitude band.
-
B.
hasZone
Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
-
C.
isInArea
Indicates that one entity is located within the spatial bounds or region defined by another entity.
-
D.
isLocatedInTimeZoneRegion
Indicates that one entity exists within or is associated with the temporal boundaries defined by a specific time zone region.
-
E.
isSouthernHemisphereTimeZone
Indicates that a time zone is located in, or primarily associated with, the Southern Hemisphere.
- 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a3db38ec8190ab5bef15bc6789be |
completed | April 20, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69e48d1b10ec8190985c6fb5766ff981 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.