Triple
T2081665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bangor television market |
E45256
|
entity |
| Predicate | hasNetworkAffiliate |
P1721
|
FINISHED |
| Object | WABI-DT2 |
E231469
|
NE 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: WABI-DT2 | Statement: [Bangor television market, hasNetworkAffiliate, WABI-DT2]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: WABI-DT2 Context triple: [Bangor television market, hasNetworkAffiliate, WABI-DT2]
-
A.
WABI-TV
chosen
WABI-TV is a long-running CBS-affiliated television station serving the Bangor, Maine market with local news, weather, and entertainment programming.
-
B.
WATH
WATH is a local radio station serving the Athens, Ohio area with news, talk, and music programming.
-
C.
WAFF
WAFF is the West Asian Football Federation, the regional governing body for football in West Asia under the Asian Football Confederation.
-
D.
WTN
WTN is the IATA airport code for RAF Waddington, a Royal Air Force station in Lincolnshire, England.
-
E.
WLBZ
WLBZ is a television station serving the Bangor, Maine market as a primary network affiliate.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a8891869c88190a02643e3bb746f59 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abbdc11a048190ba3bbc60f90f34e1 |
completed | March 7, 2026, 5:55 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae3056aa0c8190b19d97ac0c3bc31d |
completed | March 9, 2026, 2:28 a.m. |
Created at: March 4, 2026, 7:41 p.m.