Triple
T32430397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jimmy Callahan |
E828703
|
entity |
| Predicate | createsCoverStoryFor |
P145425
|
FINISHED |
| Object | Doug Harris |
—
|
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: Doug Harris | Statement: [Jimmy Callahan, createsCoverStoryFor, Doug Harris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createsCoverStoryFor Context triple: [Jimmy Callahan, createsCoverStoryFor, Doug Harris]
-
A.
usesCoverStory
chosen
Indicates that one entity employs a false or misleading explanation or narrative to conceal its true intentions, identity, or activities from another entity.
-
B.
locationCoverStory
Indicates that a particular location is used as a cover or front to conceal the true nature, purpose, or activities associated with something or someone.
-
C.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
D.
worksOnStoryAbout
Indicates that one entity is actively engaged in creating, developing, or contributing to a story whose subject or focus is another entity.
-
E.
createsContentAbout
Indicates that one entity produces or generates content whose subject or focus is another 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_69f3491b28bc8190b75cea7a507f337b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fec00f27988190955de6b6348a4d97 |
completed | May 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69febd52037c8190b475dbd50fdbc13e |
completed | May 9, 2026, 4:51 a.m. |
Created at: May 1, 2026, 12:54 a.m.