Triple
T3032218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBC 4 New York |
E82921
|
entity |
| Predicate | usesChannelNumberInBranding |
P45105
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [NBC 4 New York, usesChannelNumberInBranding, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesChannelNumberInBranding Context triple: [NBC 4 New York, usesChannelNumberInBranding, 4]
-
A.
hasBranding
Indicates that one entity carries, displays, or is associated with the brand identity of another entity.
-
B.
ownedStationsBranding
Indicates that a particular branding is used by stations that are owned by a specified entity.
-
C.
hasSpecialtyChannel
Indicates that one entity provides or is associated with a dedicated channel focused on a particular specialty or subject area for another entity.
-
D.
usesSeparateChannelFor
Indicates that one entity communicates with or accesses another entity through a distinct, dedicated channel separate from other communications or interactions.
-
E.
hasOriginalProgrammingBrand
Indicates that an entity is associated with or produced under a particular original programming brand or label.
- 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_69ad8b21a62881908ec5dd4fba4a187c |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9aefc2dc8190ad9b349ca45b7e30 |
completed | March 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69ad961e2a408190afb1759132701305 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97ba55dc8190b6dddddfb751cf64 |
completed | March 8, 2026, 3:37 p.m. |
Created at: March 8, 2026, 3:01 p.m.