Triple
T7701467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rete Ferroviaria Italiana |
E174505
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | RFI |
E682912
|
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: RFI | Statement: [Rete Ferroviaria Italiana, hasAbbreviation, RFI]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFI Context triple: [Rete Ferroviaria Italiana, hasAbbreviation, RFI]
-
A.
RFI
chosen
RFI is the Italian state-owned company responsible for managing and maintaining Italy’s national railway infrastructure.
-
B.
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.
-
C.
RF
RF is the stock ticker symbol for Regions Financial Corporation, a major U.S. regional bank headquartered in Birmingham, Alabama.
-
D.
.rf
.rf is the Cyrillic country-code top-level domain representing the Russian Federation on the internet.
-
E.
RFA
RFA is the ship prefix used by vessels of the Royal Fleet Auxiliary, the civilian-manned fleet that supports the United Kingdom’s Royal Navy with logistical and operational services.
- 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_69c6995a72cc8190998e56daa6f8e453 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70288d02c819093d6f0e47707d0a3 |
completed | March 27, 2026, 10:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8b502ebc0819095b0dc7096c2b997 |
completed | March 29, 2026, 5:13 a.m. |
Created at: March 27, 2026, 4:03 p.m.