Triple
T31599781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MNTV |
E806318
|
entity |
| Predicate | weekendProgramming |
P172008
|
FINISHED |
| Object | movie blocks |
—
|
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: movie blocks | Statement: [MNTV, weekendProgramming, movie blocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weekendProgramming Context triple: [MNTV, weekendProgramming, movie blocks]
-
A.
programming
Indicates that an entity writes, develops, or modifies software or code, typically using a programming language to create or control computer programs.
-
B.
providedProgramming
Indicates that one entity supplied or made available programming (such as software, code, or a program) to another entity.
-
C.
programmingBy
Indicates that one entity is created, implemented, or developed through the act of programming performed by another entity.
-
D.
program
Indicates that an entity creates, writes, or develops a computer program or software application.
-
E.
programChallenged
Indicates that one entity has formally questioned, disputed, or sought to overturn a program, plan, or initiative associated with another entity.
- 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_69f348d54ccc8190a03b5df9a2b40b25 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a956e9b08190bf83547bba8e8147 |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8036ab481908019f2f071fa406e |
completed | May 3, 2026, 1:42 a.m. |
Created at: April 30, 2026, 10:32 p.m.