Triple
T3871166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KDKA (AM) |
E92387
|
entity |
| Predicate | regulatorIdentifier |
P3732
|
FINISHED |
| Object | FCC Facility ID 25438 |
—
|
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: FCC Facility ID 25438 | Statement: [KDKA (AM), regulatorIdentifier, FCC Facility ID 25438]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatorIdentifier Context triple: [KDKA (AM), regulatorIdentifier, FCC Facility ID 25438]
-
A.
regulatorType
Indicates the specific kind or category of regulatory role or authority associated with an entity.
-
B.
regulatorEstablished
Indicates that an entity has formally created, instituted, or set up a regulatory body or authority.
-
C.
identifierFor
chosen
Indicates that one entity serves as a unique identifying label or code for another entity.
-
D.
regulatoryType
Indicates the specific kind or category of regulatory control, rule, or oversight that applies in the given relationship.
-
E.
regulatingAgency
Indicates that one entity serves as the official authority responsible for overseeing, controlling, or enforcing rules and standards on another entity or activity.
- 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_69aed967448c819086c4b358d37b25aa |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec54b0848190a8d4a0e4df7b6227 |
completed | March 9, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69aee754dddc8190936e1f9c40a770db |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:20 p.m.