Triple
T38136677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurricane Isaac |
E952368
|
entity |
| Predicate | nameReusedInLaterSeasons |
P34101
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Hurricane Isaac, nameReusedInLaterSeasons, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameReusedInLaterSeasons Context triple: [Hurricane Isaac, nameReusedInLaterSeasons, yes]
-
A.
nameReusedFor
chosen
Indicates that an existing name has been used again for a different entity or instance, rather than introducing a completely new name.
-
B.
recurringCharacterInSeason
Indicates that a character appears repeatedly across multiple episodes within a specific season of a series.
-
C.
usesRecurringProtagonistName
Indicates that a work repeatedly features the same protagonist character under a consistent name across multiple installments or stories.
-
D.
playedMoreThanTenSeasonsIn
Indicates that an entity participated as a player in a particular league, team, or competition for more than ten seasons.
-
E.
nameUsedBefore
Indicates that a particular name has been used or referenced at an earlier time or in a prior context relative to the current one.
- 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_69f76f09a7148190a4b91c0bacdc127a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcb089a8f881909aa9e722babd43f7 |
completed | May 7, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_69fc45666c5c8190913bd632ac0e5b84 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.