Triple
T15661391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RCTP |
E376573
|
entity |
| Predicate | IATAcode |
P418
|
FINISHED |
| Object | TPE |
E22639
|
NE 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: TPE | Statement: [RCTP, IATAcode, TPE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TPE Context triple: [RCTP, IATAcode, TPE]
-
A.
TPE
chosen
TPE is the three-letter IOC and international sporting code used to represent Chinese Taipei (Taiwan) in global competitions and events.
-
B.
TPU
TPU is a common abbreviation used by the U.S. Army Reserve to refer to its Troop Program Units, which are reserve units that train regularly but are not on active duty.
-
C.
TPU
A TPU (Tensor Processing Unit) is a specialized hardware accelerator designed by Google to efficiently perform large-scale machine learning and deep learning computations.
-
D.
TEP
TEP is the stock ticker symbol for Teleperformance, a global leader in outsourced customer experience management and business process outsourcing services.
-
E.
TPA
TPA is an abbreviation commonly used for a Tri-Party Agreement, a legal contract involving three separate parties that defines their respective rights and obligations.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85cd1564c8190991adda63bfab4b0 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ef4e6a08190ad8bbafaa3612f22 |
completed | April 16, 2026, 2:52 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff679e0f2c8190bbcb7051c38e1580 |
completed | May 9, 2026, 4:58 p.m. |
Created at: April 10, 2026, 4:15 a.m.