Triple
T3871134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KDKA (AM) |
E92387
|
entity |
| Predicate | facilityId |
P51591
|
FINISHED |
| Object | 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: 25438 | Statement: [KDKA (AM), facilityId, 25438]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: facilityId Context triple: [KDKA (AM), facilityId, 25438]
-
A.
facility
Indicates that one entity is a building, installation, or physical infrastructure used to host, support, or enable the operations or activities of another entity.
-
B.
userFacility
Indicates a relationship where a user is associated with, has access to, or operates within a particular facility.
-
C.
practiceFacility
Indicates that a location serves as a facility where individuals or groups regularly practice a particular activity, skill, or sport.
-
D.
legacyFacilityOf
Indicates that one facility is an older, predecessor, or superseded version of another facility within the same organizational or operational context.
-
E.
servesFacility
Indicates that one entity provides services or support to a particular facility as its client, target, or area of operation.
- 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_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. |
| PDg | Predicate description generation | batch_69aee80858a481909961a33fb50ff8d1 |
completed | March 9, 2026, 3:32 p.m. |
Created at: March 9, 2026, 3:20 p.m.