Triple
T19504053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pennsylvania State Police |
E487973
|
entity |
| Predicate | operatesHotline |
P5884
|
FINISHED |
| Object | Pennsylvania State Police tip line |
—
|
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: Pennsylvania State Police tip line | Statement: [Pennsylvania State Police, operatesHotline, Pennsylvania State Police tip line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesHotline Context triple: [Pennsylvania State Police, operatesHotline, Pennsylvania State Police tip line]
-
A.
operatesEmergencyNumber
Indicates that an entity is responsible for running or managing an emergency telephone number service for another entity or region.
-
B.
operatesNonEmergencyNumber
Indicates that an entity is responsible for running or managing a telephone number designated for non-emergency inquiries or services.
-
C.
operatesService
chosen
Indicates that an agent runs, manages, or provides a particular service.
-
D.
hasCallCenter
Indicates that an entity operates, is associated with, or is served by a call center.
-
E.
operateIn
Indicates that an entity performs its activities, functions, or services within a specified location, context, or domain.
- 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_69d8e8d9d1c88190b01cd78b8be49384 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e635105db8819084915dc2d047188d |
completed | April 20, 2026, 2:15 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7bd25881908caa04eaef1f6718 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:40 p.m.