Triple
T1604433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Rapids Griffins |
E34467
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | GRG |
E34467
|
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: GRG | Statement: [Grand Rapids Griffins, abbreviation, GRG]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GRG Context triple: [Grand Rapids Griffins, abbreviation, GRG]
-
A.
GRG
chosen
GRG is the standard abbreviation for the Grand Rapids Griffins, a professional ice hockey team in the American Hockey League.
-
B.
GRC
GRC is the commonly used abbreviation for NASA's Glenn Research Center, a major research facility focused on aeronautics and space technology.
-
C.
GRC
GRC is the French-language abbreviation for the Royal Canadian Mounted Police, Canada’s federal and national police service.
-
D.
GR-F
GR-F is the ISO 3166-2 regional code assigned to the Greek administrative region of Thessaly.
-
E.
GER
GER is the official FIFA country code used to represent the Germany national football team in international competitions and records.
- 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_69a885fea6a481909fe83ba6441f1774 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9094f96ec819090286c21b3dfddd5 |
completed | March 5, 2026, 4:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad51bcdebc81909520786c560598b6 |
completed | March 8, 2026, 10:38 a.m. |
Created at: March 4, 2026, 7:28 p.m.