Triple
T21989599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XPointer |
E543047
|
entity |
| Predicate | usedWith |
P4791
|
FINISHED |
| Object | XLink hyperlinks |
—
|
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 hyperlinks | Statement: [XPointer, usedWith, XLink hyperlinks]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: XLink hyperlinks Context triple: [XPointer, usedWith, XLink hyperlinks]
-
A.
XLink
chosen
XLink is an XML standard that extends basic linking capabilities by enabling rich, multidirectional, and metadata-enhanced hyperlinks between resources.
-
B.
Web Linking
Web Linking is a standardized mechanism for expressing typed relationships between web resources using link relations in HTTP headers and HTML.
-
C.
ELink
ELink is an NCBI E-utilities tool that retrieves and navigates links between related records across NCBI databases.
-
D.
XPointer
XPointer is a W3C specification that extends XPath to allow precise addressing and linking to specific parts or fragments within XML documents.
-
E.
Object Linking and Embedding
Object Linking and Embedding (OLE) is a Microsoft technology that enables embedding and linking to documents and other objects across different applications within the Windows environment.
- 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.