Triple
T19452960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bill Chapman (father) |
E486660
|
entity |
| Predicate | workOfFictionFormat |
P16443
|
FINISHED |
| Object | television series |
—
|
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: television series | Statement: [Bill Chapman (father), workOfFictionFormat, television series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workOfFictionFormat Context triple: [Bill Chapman (father), workOfFictionFormat, television series]
-
A.
hasFormatInFiction
Indicates that a work of fiction is presented or realized in a particular narrative or media format (e.g., novel, film, comic).
-
B.
hasFictionComponent
Indicates that something includes, contains, or is composed in part of a fictional element or work.
-
C.
fictionalMedium
chosen
Indicates that a work of fiction is presented or conveyed through a particular medium or format (such as a book, film, game, or comic).
-
D.
workInFiction
Indicates that one entity is a fictional work in which the other entity appears or is set.
-
E.
literaryGenreOfWork
Indicates that a work belongs to or is classified under a particular literary genre.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6339407a08190a3e0213bfbb4df3d |
completed | April 20, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.