Triple
T21990148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XML Base |
E543060
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | XLink |
—
|
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: XLink | Statement: [XML Base, relatedTo, XLink]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: XLink Context triple: [XML Base, relatedTo, XLink]
-
A.
XLink
chosen
XLink is an XML standard that extends basic linking capabilities by enabling rich, multidirectional, and metadata-enhanced hyperlinks between resources.
-
B.
ELink
ELink is an NCBI E-utilities tool that retrieves and navigates links between related records across NCBI databases.
-
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.
Linky
Linky is a French smart electricity meter system deployed nationwide to enable remote readings, real-time consumption monitoring, and improved grid management.
-
E.
U Link
U Link is a successor student-focused service platform that continues and modernizes the functions previously provided under the name University Link.
- 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_69e0c48136b081908831fa907cc02e18 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1270cb67c81909a3aa2dc61c1894f |
completed | April 28, 2026, 9:30 p.m. |
Created at: April 16, 2026, 8:05 p.m.