Triple
T10219875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ABC Radio Network |
E242546
|
entity |
| Predicate | hasClients |
P33576
|
FINISHED |
| Object | local radio stations in the United States |
—
|
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: local radio stations in the United States | Statement: [ABC Radio Network, hasClients, local radio stations in the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClients Context triple: [ABC Radio Network, hasClients, local radio stations in the United States]
-
A.
hasClient
Indicates that an entity maintains a client relationship with another entity, typically as a provider of goods or services.
-
B.
hasCustomers
chosen
Indicates that an entity maintains a business relationship in which other entities purchase or receive its goods or services as customers.
-
C.
hasClientGroup
Indicates that an entity is associated with, or belongs to, a particular group of clients.
-
D.
hasNotableClientWork
Indicates that an entity has performed significant or noteworthy work or services for a particular client.
-
E.
hasNotableClientType
Indicates that an entity has clients belonging to a particular notable or distinguished category or type.
- 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_69d381ae26c48190985abd0e25ee5d04 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d3aa715a3c8190a9ccee7bcece0346 |
completed | April 6, 2026, 12:43 p.m. |
| PD | Predicate disambiguation | batch_69d3955f61f88190b8d37ff645cd44d3 |
completed | April 6, 2026, 11:13 a.m. |
Created at: April 6, 2026, 11:08 a.m.