Triple

T26255616
Position Surface form Disambiguated ID Type / Status
Subject National Domestic Violence Hotline E656705 entity
Predicate hasTollFreeNumber P64214 FINISHED
Object 1-800-799-SAFE 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: 1-800-799-SAFE | Statement: [National Domestic Violence Hotline, hasTollFreeNumber, 1-800-799-SAFE]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTollFreeNumber
Context triple: [National Domestic Violence Hotline, hasTollFreeNumber, 1-800-799-SAFE]
  • A. hasTollFreeSection
    Indicates that a route, road, or transportation facility includes at least one segment where no toll is charged for use.
  • B. tollFreeBridgedWith
    Indicates that a toll-free communication channel is connected or linked via a bridging mechanism to another network, system, or call path.
  • C. tollFreePrefixExample
    Indicates that the subject is an example of a telephone number prefix that designates a toll-free calling number.
  • D. tollFreeForMostSections
    Indicates that the majority of sections within something (such as a route, service, or facility) can be used without paying a toll.
  • E. hasCallInNumber chosen
    Indicates that an entity has an associated telephone number designated for receiving incoming calls.
  • 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_69f674e06c9481909ed0ea736408f0d7 completed May 2, 2026, 10:04 p.m.
PD Predicate disambiguation batch_69f673c2f81c8190bf369226306eef09 completed May 2, 2026, 9:59 p.m.
Created at: April 26, 2026, 9:08 p.m.