Triple
T22775258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Highland Football League |
E563678
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | HFL |
—
|
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: HFL | Statement: [Highland Football League, abbreviation, HFL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HFL Context triple: [Highland Football League, abbreviation, HFL]
-
A.
HFL
chosen
HFL is the commonly used abbreviation for the Highland Football League, a senior football league in the north of Scotland.
-
B.
HFF
HFF is the commonly used abbreviation for the Hellenic Football Federation, the governing body of football in Greece.
-
C.
HLF
HLF is the stock ticker symbol for Herbalife, a global multi-level marketing company that sells nutritional supplements and personal care products.
-
D.
HFC
HFC is the abbreviated name of Israel’s Home Front Command, the military body responsible for civil defense and emergency preparedness.
-
E.
HFC
HFC is the common abbreviation for Hibernian Football Club, a professional football team based in Edinburgh, 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_69e24554497c819080b996e071de27c2 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17b60eec48190b0aaf3eb7ede38d4 |
completed | April 29, 2026, 3:30 a.m. |
Created at: April 17, 2026, 3:28 p.m.