Triple
T24854152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danville Correctional Center |
E621974
|
entity |
| Predicate | hasMailServices |
P164762
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Danville Correctional Center, hasMailServices, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMailServices Context triple: [Danville Correctional Center, hasMailServices, yes]
-
A.
hasMailingList
Indicates that an entity maintains or is associated with a mailing list for sending communications to subscribers.
-
B.
hasSupportService
Indicates that one entity provides or is associated with a support-related service for another entity.
-
C.
hasMessenger
Indicates that one entity uses or is associated with another entity as a messenger or intermediary for communication.
-
D.
hasServiceTo
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
-
E.
hasDefaultMailClient
Indicates that one entity is set as the primary or default email application used by another entity for handling mail-related actions.
- 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_69e2fac297e481909d3aedc75f585e42 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f650fc44e48190bc0e0a935eac62a6 |
completed | May 2, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f650c466b881908954e43bfebae8a4 |
completed | May 2, 2026, 7:30 p.m. |
Created at: April 18, 2026, 5:21 a.m.