Triple
T14874352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MeTV |
E349826
|
entity |
| Predicate | focusesOnRerunsOf |
P31
|
FINISHED |
| Object | off-network syndicated 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: off-network syndicated series | Statement: [MeTV, focusesOnRerunsOf, off-network syndicated series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusesOnRerunsOf Context triple: [MeTV, focusesOnRerunsOf, off-network syndicated series]
-
A.
focusesOn
chosen
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
B.
reappearsIn
Indicates that an entity that previously appeared becomes present or visible again in the same or another context.
-
C.
replayedOn
Indicates that an event, performance, or recording was played again on a particular medium, platform, or channel.
-
D.
hasReenactments
Indicates that an event, scene, or situation is represented again through staged or dramatized performances.
-
E.
focusDuringRevival
Indicates that one entity maintains or directs focused attention on another entity or process during a revival event or restoration phase.
- 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_69d822ee4f408190b6ac3b2fa434f0df |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded5e3e5d48190a132f2cf012b01e2 |
completed | April 15, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69de8c1a2bcc81908f914e2e2ced65eb |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:55 a.m.