Triple
T21229234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tellme Networks |
E523159
|
entity |
| Predicate | telephoneAccessNumberType |
P143303
|
FINISHED |
| Object | toll-free numbers |
—
|
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: toll-free numbers | Statement: [Tellme Networks, telephoneAccessNumberType, toll-free numbers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: telephoneAccessNumberType Context triple: [Tellme Networks, telephoneAccessNumberType, toll-free numbers]
-
A.
telephoneStandard
Indicates that there is a relationship involving the use of a particular telephone standard or protocol for communication between entities.
-
B.
callingCodeType
Indicates the type or category of a telephone calling code associated with an entity.
-
C.
telecommunicationsType
Indicates the specific category or mode of telecommunications service or technology associated with an entity.
-
D.
callType
Indicates the category or nature of a call (such as its purpose, direction, or handling), distinguishing one kind of call from another.
-
E.
hasTelephoneService
Indicates that a subject is provided with or connected to telephone service.
- 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_69e0b512ad94819087942b2ed925185f |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e734ae60408190a9480b27d109b8fc |
completed | April 21, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_69e5f60e1a888190ba75e2e900270a4e |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f993240c8190847c0b08e65726c8 |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 3:44 p.m.