Triple
T20976528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurricane Beta |
E516639
|
entity |
| Predicate | meteorologicalBasinCode |
P42479
|
FINISHED |
| Object | AL |
—
|
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: AL | Statement: [Hurricane Beta, meteorologicalBasinCode, AL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meteorologicalBasinCode Context triple: [Hurricane Beta, meteorologicalBasinCode, AL]
-
A.
isTropicalCycloneBasin
chosen
Indicates that a given geographic region or body of water functions as a basin where tropical cyclones can form or occur.
-
B.
basinCode
Indicates that an entity is associated with a specific drainage or river basin identified by a particular code.
-
C.
climateOfBasin
Indicates the prevailing climate characteristics associated with a particular basin or drainage basin.
-
D.
basinDistrict
Indicates a relationship where an administrative or geographic district is associated with, or falls within, a particular drainage or river basin.
-
E.
basinType
Indicates the specific kind or classification of a basin associated with an entity (e.g., by form, function, or hydrological role).
- 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_69e0b4fee5ac8190875fa9ceba1a5e5e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fba4a0dc819083b90795d26adfff |
completed | April 21, 2026, 4:23 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:47 p.m.