Triple
T33557442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freddie Lyon |
E859518
|
entity |
| Predicate | isFictionalJournalistIn |
P176885
|
FINISHED |
| Object | The Hour |
—
|
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: The Hour | Statement: [Freddie Lyon, isFictionalJournalistIn, The Hour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFictionalJournalistIn Context triple: [Freddie Lyon, isFictionalJournalistIn, The Hour]
-
A.
isFictionalCharacter
Indicates that the subject is a character that exists only in fiction rather than in real life.
-
B.
hasFictionalEditor
Indicates that an entity is associated with a fictional editor character responsible for editing or overseeing its content within a narrative or fictional context.
-
C.
isFictionalPersonFrom
Indicates that a fictional person originates from or is associated with a particular place or source.
-
D.
hasFictionalAuthor
Indicates that one entity is the fictional or in-universe author of a work attributed to them.
-
E.
isFictionalBearer
Indicates that an entity serves as the (typically named) holder or possessor of something within a fictional or imaginary context.
- F. None of above. chosen
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_69f3497b2b68819093207971b5e13dc8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f70b0ca081908b24a98937e6ef66 |
completed | May 3, 2026, 7:19 a.m. |
Created at: May 1, 2026, 1:40 a.m.