Triple
T20316246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strategic Rail Authority |
E510386
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SRA |
—
|
NE NERFINISHED |
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: SRA | Statement: [Strategic Rail Authority, abbreviation, SRA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SRA Context triple: [Strategic Rail Authority, abbreviation, SRA]
-
A.
SRA
chosen
SRA is the abbreviation for the former UK government body, the Strategic Rail Authority, which was responsible for overseeing and planning the country’s rail network.
-
B.
SRL
SRL is a peer-reviewed scientific journal that publishes research and reports on seismology and earthquake science.
-
C.
SRAIL
SRAIL is the stock ticker symbol for Stadler Rail, a Swiss manufacturer of railway rolling stock and related transportation solutions.
-
D.
SASR
SASR is an elite Australian Army special forces unit renowned for its covert reconnaissance, counter-terrorism, and direct action operations.
-
E.
SLRD
SLRD is the commonly used abbreviation for the Squamish-Lillooet Regional District, a local government area in southwestern British Columbia, Canada.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4c7491c8190961113c4283b10b0 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e67787af188190bc32a3049c9c5b39 |
completed | April 20, 2026, 6:59 p.m. |
Created at: April 16, 2026, 11:19 a.m.