Triple
T22961872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish Lowland Football League |
E570921
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SLFL |
—
|
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: SLFL | Statement: [Scottish Lowland Football League, abbreviation, SLFL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SLFL Context triple: [Scottish Lowland Football League, abbreviation, SLFL]
-
A.
SLFL
chosen
SLFL is the commonly used abbreviation for the Scottish Lowland Football League, a senior football league in the fifth tier of the Scottish football pyramid.
-
B.
SFL
SFL is the commonly used abbreviation for the Swiss Super League, the top tier of professional football in Switzerland.
-
C.
SFL
SFL is the IATA airport code for São Filipe Airport, which serves the town of São Filipe on Fogo Island in Cape Verde.
-
D.
SFL
SFL is the National Rail station code for Seaforth and Litherland railway station in Merseyside, England.
-
E.
SFL
SFL is the commonly used abbreviation for the Scottish Football League, the former governing body for professional league football in Scotland.
- 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_69e245b212a88190b5259caf51606084 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181f594fc8190816418486b798198 |
completed | April 29, 2026, 3:58 a.m. |
Created at: April 17, 2026, 3:47 p.m.