Triple
T2856230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantic hurricanes |
E63206
|
entity |
| Predicate | requiresSeaSurfaceTemperature |
P43684
|
FINISHED |
| Object | at least 26.5 °C |
—
|
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: at least 26.5 °C | Statement: [Atlantic hurricanes, requiresSeaSurfaceTemperature, at least 26.5 °C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresSeaSurfaceTemperature Context triple: [Atlantic hurricanes, requiresSeaSurfaceTemperature, at least 26.5 °C]
-
A.
hasSeaCondition
Indicates that an entity is associated with or characterized by a particular state or condition of the sea.
-
B.
hasSeaIce
Indicates that one entity possesses, contains, or is covered by sea ice in relation to another context or location.
-
C.
seaDepth
Indicates the measured vertical distance from the sea surface down to the seafloor at a given location.
-
D.
appliesToSeaArea
Indicates that something (such as a rule, restriction, or designation) is relevant or valid within a specified sea area.
-
E.
isShallowSea
Indicates that a body of water is a shallow marine area, typically near coasts or continental shelves, rather than deep ocean.
- 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_69ab4c41e8c08190a9e8f5249cc12610 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf62308081908a65decdd5d6f918 |
completed | March 7, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_69abdd10aef88190b750aae07e7df4dc |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abdee94c2081908e5075e87e70780a |
completed | March 7, 2026, 8:16 a.m. |
Created at: March 6, 2026, 10:02 p.m.