Triple
T22337071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WGNQ-CD |
E552177
|
entity |
| Predicate | ownershipRelation |
P147825
|
FINISHED |
| Object | sister outlet to WLS-TV |
—
|
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: sister outlet to WLS-TV | Statement: [WGNQ-CD, ownershipRelation, sister outlet to WLS-TV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownershipRelation Context triple: [WGNQ-CD, ownershipRelation, sister outlet to WLS-TV]
-
A.
identityRelation
Indicates that two entities are in fact the very same entity, not merely similar or equivalent.
-
B.
allyRelation
Indicates a cooperative, supportive relationship in which the entities act as allies toward shared or aligned goals.
-
C.
capitalRelation
Indicates that one place serves as the capital city or administrative center of another political or geographic entity.
-
D.
subjectRelation
Indicates that one entity stands in a specified relational role or connection to another entity.
-
E.
ownershipBasedIn
Indicates that an entity’s ownership or controlling stake is primarily located, registered, or based in a particular place or jurisdiction.
- F. None of above. chosen
Provenance (4 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_69e11e494eec81909c4d2d51f69499d9 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157804e60819094e2a903ace6f4b2 |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e7300c20088190a59e5bf9e70384f3 |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:43 p.m.