Triple
T35385186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanauan, Leyte |
E1022770
|
entity |
| Predicate | wasStruckBy |
P182909
|
FINISHED |
| Object | Super Typhoon Haiyan |
—
|
NE NERFINISHED |
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: Super Typhoon Haiyan | Statement: [Tanauan, Leyte, wasStruckBy, Super Typhoon Haiyan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasStruckBy Context triple: [Tanauan, Leyte, wasStruckBy, Super Typhoon Haiyan]
-
A.
wasAHitIn
Indicates that something (such as a work, product, or performance) achieved notable success or popularity within a specified context, time period, or location.
-
B.
wasBeaten
Indicates that one entity defeated or physically overpowered another in a contest, conflict, or confrontation.
-
C.
walkOffHitBy
Indicates a game-ending situation where a batter reaches base safely on a hit that results in the immediate conclusion of the contest.
-
D.
struckByPitcher
Indicates that one entity has been hit by a ball thrown by a pitcher.
-
E.
firstStruck
Indicates that one entity was the initial party to hit, attack, or make physical contact with another in a conflict or interaction.
- F. None of above. chosen
Provenance (4 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_69f76df28d8c819089f2c5799fe7d079 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f794f50080819095ff3c2cefc74fea |
completed | May 3, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f791cad5e08190a8a04ca283dbecaa |
completed | May 3, 2026, 6:19 p.m. |
Created at: May 3, 2026, 4:03 p.m.