Triple
T13779819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Movietime |
E331103
|
entity |
| Predicate | laterProgrammingFocusOfSuccessor |
P49865
|
FINISHED |
| Object | entertainment news |
—
|
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: entertainment news | Statement: [Movietime, laterProgrammingFocusOfSuccessor, entertainment news]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterProgrammingFocusOfSuccessor Context triple: [Movietime, laterProgrammingFocusOfSuccessor, entertainment news]
-
A.
successorFocus
chosen
Indicates that one entity becomes the primary or main focus immediately after another entity in a sequence or process.
-
B.
successorProject
Indicates that one project directly follows and continues or replaces another project in sequence.
-
C.
successorProgramme
Indicates that one programme directly follows and replaces another in sequence or continuity.
-
D.
successorInProgram
Indicates that one element in a program directly follows another in the program’s execution or structural order.
-
E.
successorProcess
Indicates that one process directly follows another in a defined sequence or workflow.
- 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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02460a688190a27874f8d35819c7 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe97846c819093b00ea117b64e0d |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 10:11 p.m.