Triple
T26255615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Domestic Violence Hotline |
E656705
|
entity |
| Predicate | offersServicesInLanguage |
P112988
|
FINISHED |
| Object | Spanish |
—
|
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: Spanish | Statement: [National Domestic Violence Hotline, offersServicesInLanguage, Spanish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersServicesInLanguage Context triple: [National Domestic Violence Hotline, offersServicesInLanguage, Spanish]
-
A.
hasCustomerServiceLanguage
chosen
Indicates that an entity provides customer service in a specified language or set of languages.
-
B.
offersProgramsInLanguage
Indicates that an entity provides or conducts its programs using a specified language.
-
C.
serviceBranchLanguage
Indicates the language or languages used or officially recognized by a particular branch of a service (such as a military or organizational branch).
-
D.
serviceBrandLanguage
Indicates the language or languages in which a service brand communicates or is presented.
-
E.
currentLanguageOfServices
Indicates that a specified language is the one presently used to provide or deliver certain services.
- 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 26, 2026, 9:08 p.m.