Triple
T33209136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Strike |
E850095
|
entity |
| Predicate | authorOtherNotableWorks |
P133557
|
FINISHED |
| Object | Hawaii |
—
|
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: Hawaii | Statement: [The Strike, authorOtherNotableWorks, Hawaii]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorOtherNotableWorks Context triple: [The Strike, authorOtherNotableWorks, Hawaii]
-
A.
authorNotableWork
Indicates that a person is the creator or writer of a specific notable work, such as a book, article, or other significant publication.
-
B.
notableWorkAuthor
Indicates that one entity is the creator or author of a notable work associated with another entity.
-
C.
composerOtherNotableWorks
Indicates that a composer has other notable musical works beyond the primary one currently being referenced.
-
D.
workByAuthorAlsoKnownFor
chosen
Indicates that a work is created by an author who is also notably recognized for another specified work or contribution.
-
E.
notableWorkAs
Indicates a relationship where a particular work is recognized as a significant or distinguished creation associated with an 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
Created at: May 1, 2026, 1:30 a.m.