Triple
T28536616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Idalia |
E722178
|
entity |
| Predicate | nameListRole |
P27995
|
FINISHED |
| Object | replacement name for retired hurricane |
—
|
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: replacement name for retired hurricane | Statement: [Idalia, nameListRole, replacement name for retired hurricane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameListRole Context triple: [Idalia, nameListRole, replacement name for retired hurricane]
-
A.
roleAtNom.com
Indicates that an entity holds or performs a specific role or function at a particular nominal (named) organization or institution.
-
B.
roleInName
Indicates that a specific role, title, or position is included as part of an entity’s name or naming expression.
-
C.
namesAs
chosen
Indicates that one entity assigns or uses a particular name or label to refer to another entity.
-
D.
nicknameForRole
Indicates that one entity is an informal or alternative name commonly used to refer to a particular role or position represented by another entity.
-
E.
nameElements
Indicates that an entity assigns or specifies the names of multiple elements within a set or structure.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 3:32 a.m.