Triple
T17641971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esken Limited |
E429252
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | ESKN |
—
|
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: ESKN | Statement: [Esken Limited, hasAbbreviation, ESKN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ESKN Context triple: [Esken Limited, hasAbbreviation, ESKN]
-
A.
ESKN
chosen
ESKN is the stock ticker symbol for Esken Limited, a UK-based infrastructure and aviation services company.
-
B.
ESK
ESK is the vehicle registration code assigned to cars registered in Skierniewice, a city in central Poland.
-
C.
ESVK
ESVK is a German ice hockey club based in Kaufbeuren, Bavaria, competing in the national league system.
-
D.
SKN
SKN is the station code for South Kensington tube station, a major London Underground interchange serving the South Kensington area.
-
E.
Esk
Esk is a small rural town in South East Queensland, Australia, known for serving as a local service hub for surrounding farming communities and for its proximity to Lake Wivenhoe and the Brisbane Valley rail trail.
- 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_69d889e2c2608190b762e76d9b2262f1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46de645208190a40dcf443f8afd82 |
completed | April 19, 2026, 5:53 a.m. |
Created at: April 10, 2026, 6:03 a.m.