Triple
T16821707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great New England Hurricane of 1938 |
E408909
|
entity |
| Predicate | categoryAtLandfall |
P79576
|
FINISHED |
| Object | Category 3 |
—
|
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: Category 3 | Statement: [Great New England Hurricane of 1938, categoryAtLandfall, Category 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: categoryAtLandfall Context triple: [Great New England Hurricane of 1938, categoryAtLandfall, Category 3]
-
A.
firstCategory5LandfallDate
Indicates the date on which a storm first reached Category 5 intensity at landfall.
-
B.
landfallLocation
Indicates the geographic location where a storm or similar weather system first makes landfall.
-
C.
landfallIntensity
chosen
Indicates the strength or magnitude of a storm system at the time and location where it first makes landfall.
-
D.
firstLandfallBy
Indicates the location or entity where something (typically a storm, traveler, or object) initially makes landfall or first arrives from a journey over water or air.
-
E.
madeLandfallAt
Indicates that a storm or similar weather system has come ashore at a specific geographic location.
- 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b2e77ab88190be1ec8179251864e |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.