Triple
T22505313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teleperformance SE |
E556373
|
entity |
| Predicate | tickerSymbol |
P1447
|
FINISHED |
| Object | TEP |
—
|
NE NERFINISHED |
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: TEP | Statement: [Teleperformance SE, tickerSymbol, TEP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TEP Context triple: [Teleperformance SE, tickerSymbol, TEP]
-
A.
TEP
chosen
TEP is the stock ticker symbol for Teleperformance, a global leader in outsourced customer experience management and business process outsourcing services.
-
B.
TEP
TEP is the station code used to identify Tepalcates station in the Mexico City Metro system.
-
C.
TPE
TPE is the three-letter IOC and international sporting code used to represent Chinese Taipei (Taiwan) in global competitions and events.
-
D.
TEB
TEB is the IATA airport code for Teterboro Airport, a major general aviation and corporate jet airport serving the New York City metropolitan area in New Jersey.
-
E.
Te
Te is the Taoist concept of inner virtue or inherent power that arises from living in harmony with the Tao.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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. |
Created at: April 16, 2026, 8:50 p.m.