Triple
T9706703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eurovision Song Contest 2009 |
E234916
|
entity |
| Predicate | hostBroadcaster |
P16302
|
FINISHED |
| Object | RTR |
E452049
|
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: RTR | Statement: [Eurovision Song Contest 2009, hostBroadcaster, RTR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RTR Context triple: [Eurovision Song Contest 2009, hostBroadcaster, RTR]
-
A.
RTR
chosen
RTR is a Swiss public broadcasting division that produces and distributes radio, television, and online content in the Romansh language.
-
B.
RTR
RTR is the commonly used nickname for the Recruit Training Regiment, a military unit responsible for initial training of new recruits.
-
C.
TRR
TRR is the IATA airport code for Trincomalee Airport in Sri Lanka.
-
D.
RTRA
RTRA is the abbreviation for the Royal Tank Regiment Association, an organization that supports and connects current and former members of the Royal Tank Regiment.
-
E.
TRTS
TRTS is the commonly used abbreviation for the Taipei Metro rapid transit system serving the Taipei metropolitan area in Taiwan.
- 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_69ca84cc78808190a56f3402b7c139a7 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9da4c53c81908ba4bfe4d9ca8814 |
completed | April 1, 2026, 10:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1913aa6e4819081964cf9bcf24fca |
completed | April 4, 2026, 10:31 p.m. |
Created at: March 30, 2026, 8:19 p.m.