Triple
T28893283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lookout Point |
E732767
|
entity |
| Predicate | producesForPlatform |
P120720
|
FINISHED |
| Object | linear television |
—
|
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: linear television | Statement: [Lookout Point, producesForPlatform, linear television]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producesForPlatform Context triple: [Lookout Point, producesForPlatform, linear television]
-
A.
producesFor
Indicates that one entity creates, manufactures, or generates something specifically intended for another entity’s use, benefit, or distribution.
-
B.
platformProduced
Indicates that a platform (such as a service, system, or medium) is responsible for creating, generating, or enabling the production of a particular entity or output.
-
C.
usedOnPlatformType
Indicates that something is utilized or operates on a specific type of platform.
-
D.
worksOnPlatform
Indicates that an entity performs its functions, operations, or activities using or within a specified platform.
-
E.
distributesToPlatform
chosen
Indicates that an entity allocates or delivers its content, products, or services to a specified platform for availability or use.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: April 28, 2026, 7:56 a.m.