Triple
T661954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBC Nightly News |
E11773
|
entity |
| Predicate | alsoDistributedAs |
P10379
|
FINISHED |
| Object | online video |
—
|
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: online video | Statement: [NBC Nightly News, alsoDistributedAs, online video]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoDistributedAs Context triple: [NBC Nightly News, alsoDistributedAs, online video]
-
A.
laterDistributedOn
Indicates that something was distributed or made available at a time later than a referenced distribution or event date.
-
B.
distributesIn
Indicates that one entity allocates or hands out something (e.g., items, resources, information) within or across a specified area, group, or context.
-
C.
distributedAs
Indicates that something is allocated, delivered, or spread out according to a particular pattern, rule, or distribution scheme.
-
D.
hasDistributions
chosen
Indicates that an entity is associated with one or more distributions through which it is delivered, provided, or made available.
-
E.
distributor
Indicates that an entity is responsible for supplying, delivering, or making another entity’s products or materials available to others.
- 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_69a4932862a0819098be659c814e4981 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49fd081e8819097f289961f5eff29 |
completed | March 1, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69a49d153a948190b3ccdc331ed33617 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.