Triple
T5232154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CRGA |
E118136
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | CRGA |
E118136
|
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: CRGA | Statement: [CRGA, hasAbbreviation, CRGA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CRGA Context triple: [CRGA, hasAbbreviation, CRGA]
-
A.
CRGA
chosen
CRGA is the acronym for the Committee of Representatives of Governments and Administrations, a body that brings together governmental and administrative representatives for coordination and decision-making.
-
B.
GCR
GCR is the National Rail station code for Gloucester railway station in Gloucestershire, England.
-
C.
GCRR
GCRR is the ICAO airport code for Lanzarote Airport, the main international gateway to the island of Lanzarote in Spain’s Canary Islands.
-
D.
RCG
RCG is the abbreviated name for RCG Productions, a media production company.
-
E.
CFRG
CFRG (Crypto Forum Research Group) is an IRTF research group that focuses on the development, analysis, and standardization of modern cryptographic mechanisms used in Internet protocols.
- 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_69bd4466fb8c819083b806a79414d7e4 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b0223148190be88d737c25d60d7 |
completed | March 20, 2026, 4:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bef8154940819098ed76e14804f4b3 |
completed | March 21, 2026, 7:57 p.m. |
Created at: March 20, 2026, 1:49 p.m.