Triple
T38242736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guy Patterson |
E1013810
|
entity |
| Predicate | notableFictionalWork |
P4
|
FINISHED |
| Object | That Thing You Do! (song) |
E1831560
|
NE 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: That Thing You Do! (song) | Statement: [Guy Patterson, notableFictionalWork, That Thing You Do! (song)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFictionalWork Context triple: [Guy Patterson, notableFictionalWork, That Thing You Do! (song)]
-
A.
notableFictionalFeature
Indicates that an entity is distinguished by a specific fictional characteristic, trait, or element it is known for.
-
B.
hasFictionalWork
Indicates that one entity is the creator, owner, or source of a fictional work associated with another entity.
-
C.
notableWork
chosen
Indicates that one entity is a significant or well-known work (such as a book, artwork, or creation) produced by another entity.
-
D.
fictionalWorkTitle
Indicates the title assigned to a fictional work, such as a novel, film, or game.
-
E.
isForFictionalWork
Indicates that something is intended to be used in, associated with, or specifically created for a fictional work.
- F. None of above.
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_69f76dd7e89c8190b7866bc85aea521b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4185622a8081908ebf0d6544e75811 |
completed | June 28, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.