Triple
T4941002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Romney |
E110931
|
entity |
| Predicate | effectOfGreatStormOf1287 |
P60161
|
FINISHED |
| Object | harbour silted up |
—
|
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: harbour silted up | Statement: [New Romney, effectOfGreatStormOf1287, harbour silted up]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOfGreatStormOf1287 Context triple: [New Romney, effectOfGreatStormOf1287, harbour silted up]
-
A.
stormedOn
Indicates that a storm or severe weather event occurred affecting or impacting a particular entity or location.
-
B.
floodCause
Indicates that one entity is the cause or source of a flood affecting another entity or area.
-
C.
typicalStormType
Indicates the kind of storm that is most commonly or characteristically associated with a given context or location.
-
D.
secondMajorLandfallDate
Indicates the calendar date on which an entity, such as a storm or similar event, makes its second significant landfall.
-
E.
floodEvent
Indicates an occurrence of a flooding event affecting a location, time period, or set of impacted entities.
- 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_69bd4415eee08190bdce70276e56a5b4 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd708ba9888190baf4e79c8f159e9f |
completed | March 20, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69bd6c389b9881908ad7fb1c5393c1b1 |
completed | March 20, 2026, 3:48 p.m. |
| PDg | Predicate description generation | batch_69bd6ff85b50819081d78087caa6b473 |
completed | March 20, 2026, 4:04 p.m. |
Created at: March 20, 2026, 1:31 p.m.