Triple
T14984818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WNBC (Washington, D.C.) |
E373672
|
entity |
| Predicate | hadAudience |
P793
|
FINISHED |
| Object | regional audience in the Washington, D.C. area |
—
|
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: regional audience in the Washington, D.C. area | Statement: [WNBC (Washington, D.C.), hadAudience, regional audience in the Washington, D.C. area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadAudience Context triple: [WNBC (Washington, D.C.), hadAudience, regional audience in the Washington, D.C. area]
-
A.
hasAudienceReception
Indicates the relationship between a work or event and how it is received, perceived, or evaluated by its audience.
-
B.
filmedBeforeAudience
Indicates that the filming of an event, performance, or production took place in front of a live audience.
-
C.
hasAudience
chosen
Indicates that an entity is intended to be received, viewed, or engaged with by a particular group of people.
-
D.
hasAudienceParticipation
Indicates that an event, performance, or activity involves direct participation or interaction from the audience.
-
E.
hasAuditorium
Indicates that one entity possesses or includes an auditorium as part of its facilities.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6ff4a7c8190ab7554f3a1a09b67 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6169b48190a679609febd2d0e3 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:52 a.m.