Triple
T28738999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 12 Miles of Bad Road |
E730886
|
entity |
| Predicate | intendedChannelType |
P178772
|
FINISHED |
| Object | premium cable |
—
|
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: premium cable | Statement: [12 Miles of Bad Road, intendedChannelType, premium cable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedChannelType Context triple: [12 Miles of Bad Road, intendedChannelType, premium cable]
-
A.
intendedReceiver
Indicates that one entity is the target or designated recipient of something (such as a message, item, or action) originating from another entity.
-
B.
targetChannel
chosen
Indicates the specific channel or medium through which an action, message, or effect is directed toward its intended recipient.
-
C.
includesChannelType
Indicates that one entity encompasses or supports a specified type of communication or distribution channel as part of its structure or functionality.
-
D.
intendedEngineType
Indicates that an entity is designed or specified to use a particular type of engine.
-
E.
intendedEquipmentType
Indicates that a particular piece of equipment is the planned or designated type to be used in a given context or activity.
- 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_69f043eae0908190b28ce314686247d7 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 28, 2026, 6:02 a.m.