Triple
T16571944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Hazen |
E402608
|
entity |
| Predicate | latitudeDirection |
P124104
|
FINISHED |
| Object | north |
—
|
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: north | Statement: [Lake Hazen, latitudeDirection, north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: latitudeDirection Context triple: [Lake Hazen, latitudeDirection, north]
-
A.
geographicDirectionImpliedByName
Indicates that the name of a place or feature suggests a specific geographic direction (e.g., north, south, east, west) relative to some reference.
-
B.
directionBy
Indicates that one entity provides directional guidance, orientation, or navigational reference for another entity.
-
C.
lapDirection
Indicates the direction or orientation in which a lapping or overlapping action occurs between entities.
-
D.
latitudinalOrientation
Indicates the relative east–west positioning or alignment of one entity with respect to another based on latitude.
-
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. chosen
Provenance (4 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35959f1748190934b263d6bc94143 |
completed | April 18, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69e2d7f97e548190a474691a152bd8e8 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:16 a.m.