Triple
T8831117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleveland Monsters |
E210143
|
entity |
| Predicate | usesAbbreviation |
P43
|
FINISHED |
| Object | CLE |
E210143
|
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: CLE | Statement: [Cleveland Monsters, usesAbbreviation, CLE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CLE Context triple: [Cleveland Monsters, usesAbbreviation, CLE]
-
A.
CLE
chosen
CLE is the standard abbreviation used for the Cleveland Monsters, a professional ice hockey team in the American Hockey League.
-
B.
CLE
CLE is the three-letter IATA airport code for Cleveland Hopkins International Airport, the primary commercial airport serving the Cleveland, Ohio metropolitan area.
-
C.
CL
CL is the ticker symbol for West Texas Intermediate (WTI) crude oil futures contracts traded on the New York Mercantile Exchange (NYMEX).
-
D.
CL
CL is the common abbreviation for Japan’s professional baseball Central League.
-
E.
CL
CL is the vehicle registration code used on license plates for vehicles registered in Peru’s Callao Region.
- 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_69ca8365b28081909e48e45e95dfc405 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc604ed2b88190b4f53b34b5a438f7 |
completed | April 1, 2026, 12:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfc1bee344819084ec6e20ea01728f |
completed | April 3, 2026, 1:33 p.m. |
Created at: March 30, 2026, 6:47 p.m.