Triple
T22505335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teleperformance SE |
E556373
|
entity |
| Predicate | providesServiceForIndustry |
P112563
|
FINISHED |
| Object | telecommunications |
—
|
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: telecommunications | Statement: [Teleperformance SE, providesServiceForIndustry, telecommunications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesServiceForIndustry Context triple: [Teleperformance SE, providesServiceForIndustry, telecommunications]
-
A.
providesServices
Indicates that one entity supplies or performs services for the benefit or use of another entity.
-
B.
serviceFor
Indicates that one entity provides a service or performs functions on behalf of another entity.
-
C.
providesServiceOn
Indicates that one entity offers or performs a service during, on, or in connection with a specified time, date, or schedule.
-
D.
supportedIndustry
chosen
Indicates that one entity provides backing, resources, or services to help sustain or advance a particular industry.
-
E.
providesServiceTowards
Indicates that one entity delivers or performs a service directed to or for the benefit of another entity.
- 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15d5bf0f0819093426d83ebd80ef0 |
completed | April 29, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69e898be31448190be5ae7f5656f0497 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:50 p.m.