Triple
T3966638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Shuttle |
E92231
|
entity |
| Predicate | owner |
P347
|
FINISHED |
| Object | Getlink |
E90397
|
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: Getlink | Statement: [Le Shuttle, owner, Getlink]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Getlink Context triple: [Le Shuttle, owner, Getlink]
-
A.
Getlink
chosen
Getlink is a French-based company that owns and operates the infrastructure of the Channel Tunnel rail link between the United Kingdom and continental Europe.
-
B.
LinkPass
LinkPass is a type of transit fare product used within the same system as the CharlieTicket, providing riders with a pass-based option for public transportation access.
-
C.
Fieldlink
Fieldlink was an early digital payments and security startup co-founded by Max Levchin that later evolved into the company behind PayPal.
-
D.
The Link
The Link is a key University College Birmingham facility that provides modern teaching, learning, and student support spaces.
-
E.
Q-LINK
Q-LINK is the radio callsign used by QantasLink, the regional airline brand of Qantas Airways in Australia.
- 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_69aed96624188190ac8c45bb57ab72b5 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef976f4fc8190b2c16ab62c19cdb8 |
completed | March 9, 2026, 4:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b54006b5e48190973e30055a0893a5 |
completed | March 14, 2026, 11:01 a.m. |
Created at: March 9, 2026, 3:32 p.m.