Triple
T11440628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azores High |
E271133
|
entity |
| Predicate | typicalCenterLatitude |
P1281
|
FINISHED |
| Object | around 25–35 degrees 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: around 25–35 degrees North | Statement: [Azores High, typicalCenterLatitude, around 25–35 degrees North]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCenterLatitude Context triple: [Azores High, typicalCenterLatitude, around 25–35 degrees North]
-
A.
geographicCenter
Indicates the location that serves as the central point of a geographic area or region.
-
B.
coordinateLatitude
chosen
Indicates the north–south geographic position of an entity on the Earth’s surface, expressed as a latitude coordinate.
-
C.
centralPeak
Indicates that one entity is the central, elevated peak located near the middle of another entity, typically within a larger structure such as a crater or basin.
-
D.
centralLocation
Indicates that one entity serves as the primary or central place associated with another entity.
-
E.
centerType
Indicates the classification or category of a center (e.g., type of facility, institution, or hub) associated with an entity.
- 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_69d6aadeef688190874bcecd88b3dd9b |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d80888190c8190b6365550ffe4931c |
completed | April 9, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69d7e7162b288190a0bfb89f7eb747c7 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:35 p.m.