Triple
T16148646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regions Financial Corporation |
E391852
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | RF |
E391852
|
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: RF | Statement: [Regions Financial Corporation, hasAbbreviation, RF]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RF Context triple: [Regions Financial Corporation, hasAbbreviation, RF]
-
A.
RF
chosen
RF is the stock ticker symbol for Regions Financial Corporation, a major U.S. regional bank headquartered in Birmingham, Alabama.
-
B.
RF
RF is the commonly used abbreviation for Radio France, the French national public radio broadcasting organization.
-
C.
RF
RF was the squadron code used to identify No. 303 Polish Fighter Squadron, a renowned Polish unit that fought alongside the Royal Air Force during World War II.
-
D.
.rf
.rf is the Cyrillic country-code top-level domain representing the Russian Federation on the internet.
-
E.
RFI
RFI is the Italian state-owned company responsible for managing and maintaining Italy’s national railway infrastructure.
- 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_69d87f1c65e48190aa2b4c472e9bafc4 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21d9551e081908391061b092ff31b |
completed | April 17, 2026, 11:46 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fff7a9ebf08190aa21cdff051f4ba2 |
completed | May 10, 2026, 3:12 a.m. |
Created at: April 10, 2026, 5:01 a.m.