Triple
T11440612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azores High |
E271133
|
entity |
| Predicate | typicalPressureRange |
P13474
|
FINISHED |
| Object | about 1020–1035 hPa at sea level |
—
|
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: about 1020–1035 hPa at sea level | Statement: [Azores High, typicalPressureRange, about 1020–1035 hPa at sea level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPressureRange Context triple: [Azores High, typicalPressureRange, about 1020–1035 hPa at sea level]
-
A.
pressureRange
Indicates the range of pressure values within which a condition, process, or relationship is defined or valid.
-
B.
typicalRange
chosen
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
-
C.
typicalElevationRange
Indicates the usual range of elevation values within which something commonly occurs or exists.
-
D.
operatingPressureStandard
Indicates the standard or specified pressure level at which an operation, system, or component is intended to function.
-
E.
chamberPressure_bar
Indicates the pressure within a chamber, expressed in units of bar.
- 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.