Triple
T14286895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucy Saxon shoots the Master |
E354197
|
entity |
| Predicate | hasBroadcastYear |
P49330
|
FINISHED |
| Object | 2007 |
—
|
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: 2007 | Statement: [Lucy Saxon shoots the Master, hasBroadcastYear, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBroadcastYear Context triple: [Lucy Saxon shoots the Master, hasBroadcastYear, 2007]
-
A.
broadcastYear
chosen
Indicates the year in which something (typically a program or content) was originally broadcast.
-
B.
primaryBroadcasterFromYear
Indicates the year from which an entity began serving as the primary broadcaster for a given subject or event.
-
C.
wasBroadcastOn
Indicates that a media item (such as a program, episode, or event) was transmitted or aired via a particular broadcast channel, station, or network.
-
D.
banYear
Indicates the year in which a ban was enacted or came into effect on the related entity or activity.
-
E.
hasSpecialYear
Indicates that an entity is associated with a particular year that is distinguished or treated as exceptional in some defined context.
- 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_69d8278e17088190b328c5a9d4be74ff |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de697ef40c8190bea37724b28c2e99 |
completed | April 14, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a88446481909cd526da97a3b70f |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:11 a.m.