Triple
T29774581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sydkap Fiord region |
E755342
|
entity |
| Predicate | hasLatitudeCategory |
P13005
|
FINISHED |
| Object | high-latitude |
—
|
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: high-latitude | Statement: [Sydkap Fiord region, hasLatitudeCategory, high-latitude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLatitudeCategory Context triple: [Sydkap Fiord region, hasLatitudeCategory, high-latitude]
-
A.
liesWithinLatitudeBand
chosen
Indicates that one geographic entity is located within a specified range of latitudes defined as a latitude band.
-
B.
hasDistanceCategory
Indicates that one entity is associated with a qualitative or categorical classification of its distance relative to another entity or reference point.
-
C.
latitudeVariesOver
Indicates that the latitude of a location changes across the extent or domain of another entity (such as a region, path, or time period).
-
D.
landingLatitudeApprox
Indicates an approximate geographic latitude at which a landing event occurs.
-
E.
coordinateLatitude
Indicates the north–south geographic position of an entity on the Earth’s surface, expressed as a latitude coordinate.
- 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_69f0ef878574819088c867fd1a5c8b86 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
Created at: April 28, 2026, 8:45 p.m.