Triple
T7878293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Rapids Griffins |
E182911
|
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 French-language abbreviation for the Royal Canadian Mounted Police, Canada’s federal and national police service.
-
C.
GRC
GRC is the commonly used abbreviation for NASA's Glenn Research Center, a major research facility focused on aeronautics and space technology.
-
D.
GRJ
GRJ is the IATA airport code for George Airport, a regional airport serving the town of George in South Africa’s Western Cape province.
-
E.
GRA
GRA is the ring-shaped orbital motorway encircling Rome, Italy, serving as a major traffic artery for the metropolitan area.
- 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_69ca828a17248190b46defe758bc5ad3 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb39bd64e481909f699e7dd2818b8f |
completed | March 31, 2026, 3:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cb5b7fef308190bbc74e13f4205192 |
completed | March 31, 2026, 5:28 a.m. |
Created at: March 30, 2026, 4:57 p.m.