Triple
T15376729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Towers Watson |
E367686
|
entity |
| Predicate | tradedAs |
P2822
|
FINISHED |
| Object | TW |
E367686
|
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: TW | Statement: [Towers Watson, tradedAs, TW]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TW Context triple: [Towers Watson, tradedAs, TW]
-
A.
TW
TW is the two-letter ISO 3166 country code assigned to Taiwan (commonly referred to as Chinese Taipei in certain international contexts).
-
B.
TW
TW is the IATA airline designator assigned to T’way Air, a South Korean low-cost carrier.
-
C.
TW
TW is a UK postcode area in southwest London and parts of Surrey, covering towns such as Twickenham and Staines-upon-Thames.
-
D.
TW
chosen
TW is the stock ticker symbol for Towers Watson, a global professional services firm specializing in risk management, insurance brokerage, and human resources consulting.
-
E.
TW
TW is the former IATA airline designator for Trans World Airlines, a major historic American international carrier.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e5ece1081908d7c1289258b9c1f |
completed | April 16, 2026, 1:41 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff0b5502508190bd39b6d81ee57cc0 |
completed | May 9, 2026, 10:24 a.m. |
Created at: April 10, 2026, 3:18 a.m.