Triple
T11402137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allison |
E270137
|
entity |
| Predicate | namingListType |
P5109
|
FINISHED |
| Object | Atlantic hurricane naming list |
—
|
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: Atlantic hurricane naming list | Statement: [Allison, namingListType, Atlantic hurricane naming list]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namingListType Context triple: [Allison, namingListType, Atlantic hurricane naming list]
-
A.
onNameTypeLists
Indicates that something appears on one or more lists that are categorized or organized by name type.
-
B.
listType
chosen
Indicates that one entity specifies the classification or category type of a list associated with another entity.
-
C.
nameType
Indicates the specific category or type of a name associated with an entity (e.g., legal name, nickname, alias, or preferred name).
-
D.
listingType
Indicates the category or format under which an item, property, or service is offered or advertised (e.g., for sale, for rent, auction, etc.).
-
E.
namingStructure
Indicates a relationship where one entity defines, organizes, or constrains the naming or label format used for another entity.
- 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_69d6aacdbc6c8190af6dc3d5f5d22836 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d80148e2048190a716b515d78efdd1 |
completed | April 9, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69d7e70ffd708190b62a78ebcbce9f78 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.