Triple
T4739558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toronto Toros |
E105204
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | TOR |
E84202
|
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: TOR | Statement: [Toronto Toros, hasAbbreviation, TOR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TOR Context triple: [Toronto Toros, hasAbbreviation, TOR]
-
A.
TOR
TOR is the official code designation used for the Georgian football club FC Torpedo Kutaisi.
-
B.
TOR
chosen
TOR is the standard three-letter abbreviation used to represent the Toronto Maple Leafs in sports standings, statistics, and media.
-
C.
TER
TER is the IATA airport code for Lajes Airport on Terceira Island in the Azores, Portugal.
-
D.
TER
TER is a network of regional express trains in France that provides local passenger rail services across various regions.
-
E.
Tur
Tur is a foundational 14th-century Jewish legal code by Rabbi Jacob ben Asher that systematically organized halakhic rulings and served as a primary basis for later works like the Shulchan Aruch.
- 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_69bd43ef87a48190a5bc3600711aa032 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6486f8608190908e43b777810c44 |
completed | March 20, 2026, 3:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be3a1796608190972865b2f6beef05 |
completed | March 21, 2026, 6:26 a.m. |
Created at: March 20, 2026, 1:19 p.m.