Triple
T22166229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WXTV-DT |
E547794
|
entity |
| Predicate | FCCFacilityType |
P111465
|
FINISHED |
| Object | full-power television station |
—
|
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: full-power television station | Statement: [WXTV-DT, FCCFacilityType, full-power television station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FCCFacilityType Context triple: [WXTV-DT, FCCFacilityType, full-power television station]
-
A.
fccFacilityType
chosen
Indicates the specific type or classification of a facility as defined by the FCC (Federal Communications Commission).
-
B.
designedFacilityType
Indicates the type or category of facility that something (such as a plan, system, or component) is specifically designed for.
-
C.
typeOfPortFacility
Indicates that one port facility is classified as a specific type or category of port facility in relation to another.
-
D.
investigatedFacilityType
Indicates that an entity has conducted an investigation specifically targeting a facility of the given type.
-
E.
productionFacilityType
Indicates the specific kind or category of facility where production or manufacturing activities take place.
- 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_69e11e3c4c5c81908d336165816b12e0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12a314cc081908857c13d018d52b2 |
completed | April 28, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69e71b41555881909b8e22718974d527 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:34 p.m.