Triple
T15231247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LLOY |
E364006
|
entity |
| Predicate | exchangeMic |
P2798
|
FINISHED |
| Object | XLON |
E786154
|
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: XLON | Statement: [LLOY, exchangeMic, XLON]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: XLON Context triple: [LLOY, exchangeMic, XLON]
-
A.
XLON
chosen
XLON is the Market Identifier Code for the London Stock Exchange, one of the world’s largest and most prominent stock markets.
-
B.
HXL
HXL (Humanitarian Exchange Language) is a lightweight data standard designed to improve the interoperability, quality, and rapid sharing of humanitarian data across organizations and crises.
-
C.
XRL
XRL is a high-speed rail line connecting Guangzhou, Shenzhen, and Hong Kong, forming a key part of China’s national high-speed railway network.
-
D.
XL
XL is the IATA airline designator used for LATAM Airlines Ecuador, a regional carrier based in Ecuador and part of the LATAM Airlines Group.
-
E.
Xelb
Xelb is the former Arabic name for the Portuguese city of Silves, a historically significant town in the Algarve region.
- 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0078e27408190bc13c0ca441f5594 |
completed | April 15, 2026, 9:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fedd3beae88190a91af2c9a7def8f8 |
completed | May 9, 2026, 7:07 a.m. |
Created at: April 10, 2026, 3:12 a.m.