Triple
T10289945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheffield Midland |
E241335
|
entity |
| Predicate | stationCode |
P1289
|
FINISHED |
| Object | SHF |
E241334
|
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: SHF | Statement: [Sheffield Midland, stationCode, SHF]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SHF Context triple: [Sheffield Midland, stationCode, SHF]
-
A.
SHF
chosen
SHF is the National Rail station code for Sheffield railway station, a major rail hub in South Yorkshire, England.
-
B.
SH
SH is the common abbreviation for Södertörn University, a higher education institution located in the Stockholm region of Sweden.
-
C.
SH
SH is the vehicle registration code for the Swiss canton of Schaffhausen.
-
D.
SH8
SH8 is a scenic coastal highway in southern Albania that winds along the Albanian Riviera, connecting key seaside towns and offering views of the Ionian Sea.
-
E.
SH4
SH4 is a 32-bit RISC microprocessor architecture from Hitachi’s SuperH family, widely used in embedded systems and notably in the Sega Dreamcast console.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2d192288190a64c27a4f26b71fc |
completed | April 7, 2026, 9:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d6f85dcbac8190a2ac66354010e328 |
completed | April 9, 2026, 12:52 a.m. |
Created at: April 6, 2026, 11:41 a.m.