Triple
T31810801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyasina Bay |
E811999
|
entity |
| Predicate | latitudeZone |
P40151
|
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: [Pyasina Bay, latitudeZone, high latitude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: latitudeZone Context triple: [Pyasina Bay, latitudeZone, high latitude]
-
A.
latitudeRegion
chosen
Indicates that an entity is located within, or associated with, a specific geographic region defined by latitude coordinates.
-
B.
zoneType
Indicates the classification or category of a zone that specifies its type or functional designation.
-
C.
zoneAuthority
Indicates that an entity has official control, responsibility, or decision-making power over a specific zone or area.
-
D.
zone
Indicates that an entity is located within, associated with, or assigned to a particular geographic or conceptual area or zone.
-
E.
timeZoneArea
Indicates the geographic area or region for which a particular time zone is defined or applicable.
- 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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:43 p.m.