Triple
T14696575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hathaway Man campaign |
E345177
|
entity |
| Predicate | creativeDevice |
P43299
|
FINISHED |
| Object | mysterious eyepatch as attention‑getting hook |
—
|
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: mysterious eyepatch as attention‑getting hook | Statement: [Hathaway Man campaign, creativeDevice, mysterious eyepatch as attention‑getting hook]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creativeDevice Context triple: [Hathaway Man campaign, creativeDevice, mysterious eyepatch as attention‑getting hook]
-
A.
builtDevice
Indicates that one entity constructed or assembled a device for or associated with another entity.
-
B.
notableGadget
Indicates that an entity is a gadget that is recognized as notable, significant, or widely known in some context.
-
C.
typicalGadgets
Indicates that the associated items are commonly used or standard gadgets typically found or expected in a given context.
-
D.
device
chosen
Indicates that one entity is a device used, controlled, or referenced by another entity in the relationship.
-
E.
technologyInteractedWith
Indicates that an entity has used, engaged with, or otherwise interacted with a particular technology.
- 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_69d822e4a8c08190a155df736bb7bc13 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb58855e081908b38f9515db5677f |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de657c57ec8190ae0b9bb79a514566 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.