Triple
T28156540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Williams Street |
E714763
|
entity |
| Predicate | notableBlockProduced |
P202541
|
FINISHED |
| Object | Toonami |
—
|
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: Toonami | Statement: [Williams Street, notableBlockProduced, Toonami]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBlockProduced Context triple: [Williams Street, notableBlockProduced, Toonami]
-
A.
notableBlock
Indicates that one entity is a block (e.g., text, code, or content segment) that is considered notable or significant in relation to another entity or context.
-
B.
notableMiner
Indicates that an entity is recognized as a miner of particular significance or prominence.
-
C.
notableTransaction
Indicates that a transaction between entities is significant or noteworthy in context, such as being unusually large, important, or otherwise exceptional.
-
D.
firstBlockMinedDate
Indicates the date on which the first block associated with the entity was mined.
-
E.
notableSeed
Indicates that an entity is a seed that is particularly significant, prominent, or noteworthy in some context.
- 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_69efd6b156448190bfa15958208395c3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_6a008ebb22408190a2293bced40a7e53 |
completed | May 10, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_6a008e8715dc8190ab23292605901bf4 |
completed | May 10, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_6a008eba6de8819083165152448f6071 |
completed | May 10, 2026, 1:57 p.m. |
Created at: April 27, 2026, 10:03 p.m.