Triple
T32132115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mission Broadcasting, Inc. |
E820678
|
entity |
| Predicate | ownsStationType |
P53258
|
FINISHED |
| Object | full-power television stations |
—
|
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 stations | Statement: [Mission Broadcasting, Inc., ownsStationType, full-power television stations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownsStationType Context triple: [Mission Broadcasting, Inc., ownsStationType, full-power television stations]
-
A.
ownedStation
chosen
Indicates that one entity possesses ownership or control over a particular station.
-
B.
hasStationTypeAt
Indicates that a specific type of station is present or assigned at a particular location or point.
-
C.
ownsLicenseForStationType
Indicates that an entity holds a valid license authorizing operation or use of a specific type of station.
-
D.
hasStationHouseType
Indicates the specific type or classification of a station house associated with an entity.
-
E.
isStationOf
Indicates that a given location functions as a station (e.g., transport or service hub) associated with or serving a particular system, line, route, or organization.
- 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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b9726c848190bd8a36c32c389f2e |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:29 a.m.