Triple
T3897161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Getlink |
E90397
|
entity |
| Predicate | hasBrand |
P1500
|
FINISHED |
| Object | ElecLink |
E397096
|
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: ElecLink | Statement: [Getlink, hasBrand, ElecLink]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ElecLink Context triple: [Getlink, hasBrand, ElecLink]
-
A.
ElecLink
chosen
ElecLink is a high-voltage direct current electricity interconnector project linking the power grids of the United Kingdom and France through the Channel Tunnel.
-
B.
Cylink Corporation
Cylink Corporation was a pioneering American company specializing in data encryption and network security technologies, particularly for government and enterprise communications.
-
C.
Q-LINK
Q-LINK is the radio callsign used by QantasLink, the regional airline brand of Qantas Airways in Australia.
-
D.
EasyLink
EasyLink is Philips' trade name for its HDMI-CEC feature that lets connected HDMI devices control each other with a single remote.
-
E.
Link 2 Line
Link 2 Line is a light rail service in the Seattle metropolitan area that connects key neighborhoods and suburbs as part of the Sound Transit Link system.
- 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_69aed95d315881908cbf1bf4a7215fbf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeecd34e608190bf1ca1d0c04562b2 |
completed | March 9, 2026, 3:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5285093208190a2ba00afcbd8a261 |
completed | March 14, 2026, 9:20 a.m. |
Created at: March 9, 2026, 3:21 p.m.