Triple
T23004282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toledo Walleye |
E572717
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | TOL |
—
|
NE NERFINISHED |
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: TOL | Statement: [Toledo Walleye, hasAbbreviation, TOL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TOL Context triple: [Toledo Walleye, hasAbbreviation, TOL]
-
A.
TOL
chosen
TOL is the standard abbreviation for the Toledo Walleye, a professional minor league ice hockey team based in Toledo, Ohio.
-
B.
TOL
TOL is the IATA airport code for Toledo Express Airport, a public airport serving the Toledo, Ohio area in the United States.
-
C.
TÖL
TÖL is the German vehicle registration code assigned to the district of Bad Tölz-Wolfratshausen in Bavaria.
-
D.
TLO
TLO, also known as Dario Wünsch, is a German professional StarCraft II player renowned for his creative strategies and long-standing presence in the competitive scene.
-
E.
TLO
TLO is the official online portal providing public access to information, documents, and tracking tools for the Texas Legislature’s activities and legislation.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e245b6a3ac81908087599eefe3e365 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f183556cd08190b18780680bc4f23e |
completed | April 29, 2026, 4:04 a.m. |
Created at: April 17, 2026, 3:51 p.m.