Triple
T33414162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zotz! |
E855666
|
entity |
| Predicate | hasTitleCharacterUtterance |
P146200
|
FINISHED |
| Object | The word "Zotz" activates the amulet's powers |
—
|
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: The word "Zotz" activates the amulet's powers | Statement: [Zotz!, hasTitleCharacterUtterance, The word "Zotz" activates the amulet's powers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleCharacterUtterance Context triple: [Zotz!, hasTitleCharacterUtterance, The word "Zotz" activates the amulet's powers]
-
A.
hasTitleCharacterAction
Indicates that a work’s title explicitly references or is derived from an action performed by a character within that work.
-
B.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
-
C.
hasTitleOf
Indicates that one entity holds, bears, or is designated by the official title, name, or rank specified by another entity.
-
D.
hasTitleLetter
Indicates that an entity possesses a specific letter or character within its title.
-
E.
hasTitleCharacterFrom
chosen
Indicates that a work has a title that includes or is derived from a specific character.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: May 1, 2026, 1:36 a.m.