Triple
T21106006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurricane Epsilon |
E520044
|
entity |
| Predicate | affectedLand |
P142870
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Hurricane Epsilon, affectedLand, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectedLand Context triple: [Hurricane Epsilon, affectedLand, false]
-
A.
affectedArea
Indicates the specific region or extent over which an event, condition, or influence has an impact.
-
B.
areaDestroyed
Indicates that a specified portion or region has been damaged or ruined to the point of destruction.
-
C.
affectedCountry
Indicates that a particular country is impacted or influenced by an event, action, or condition.
-
D.
landAction
Indicates an action in which an entity comes down to and makes contact with a surface or ground, typically concluding a movement through air or space.
-
E.
territorialConsequence
Indicates the resulting change or effect on territorial control, boundaries, or status that follows from a particular event, action, or condition.
- 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_69e0b509a318819092fbbcb21d1fe603 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e71b62301c819082cfc6cb3cd11c8c |
completed | April 21, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69e5dbff56848190a03b350a9305c612 |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2e03d88819086f8b641656ad8b0 |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 2:53 p.m.