Triple
T29953248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Pacific Hurricane Center |
E760823
|
entity |
| Predicate | issuesProducts |
P1557
|
FINISHED |
| Object | tropical cyclone discussions |
—
|
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: tropical cyclone discussions | Statement: [Central Pacific Hurricane Center, issuesProducts, tropical cyclone discussions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuesProducts Context triple: [Central Pacific Hurricane Center, issuesProducts, tropical cyclone discussions]
-
A.
issues
chosen
Indicates that an entity formally produces, releases, or distributes something, such as a document, order, or resource, making it officially available.
-
B.
productWith
Indicates a relationship where one entity is associated with, contains, or is offered together with another entity as a product.
-
C.
productsUsedIn
Indicates that certain products are utilized or applied within a particular process, context, or entity.
-
D.
byProduct
Indicates that one entity is produced incidentally or as a secondary result of a process, activity, or creation involving another entity.
-
E.
usesProduct
Indicates that one entity makes use of, applies, or employs a particular product.
- 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_69f2246562b881909d57622f4086d43d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 29, 2026, 6:26 p.m.