Triple
T16989558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trades Union Congress |
E412156
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | TUC |
E412156
|
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: TUC | Statement: [Trades Union Congress, shortName, TUC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TUC Context triple: [Trades Union Congress, shortName, TUC]
-
A.
TUC
TUC is the commonly used abbreviation for the Technical University of Crete, a Greek public university specializing in engineering and applied sciences.
-
B.
TUC
chosen
TUC is the main national federation of trade unions in England and Wales, representing millions of workers and coordinating union activities and campaigns.
-
C.
TUC
TUC is the standard abbreviation used for the Tucson Roadrunners, a professional ice hockey team in the American Hockey League.
-
D.
TUC
TUC is the standard abbreviation for the Tucson Saguaros, a professional baseball team based in Tucson, Arizona.
-
E.
TUC Regions
TUC Regions are the regional divisions of the Trades Union Congress that coordinate and support trade union activity and campaigns across different parts of the UK.
- 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_69d886cb581c8190ab05f4b429c9cd85 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d27dca248190a9b73b16439d5631 |
completed | April 18, 2026, 6:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00dc14d5688190945f7ae72f724922 |
completed | May 10, 2026, 7:27 p.m. |
Created at: April 10, 2026, 5:32 a.m.