Triple
T20803676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XBRL |
E512102
|
entity |
| Predicate | hasComponent |
P35
|
FINISHED |
| Object | XBRL linkbase |
—
|
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: XBRL linkbase | Statement: [XBRL, hasComponent, XBRL linkbase]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: XBRL linkbase Context triple: [XBRL, hasComponent, XBRL linkbase]
-
A.
XBRL
chosen
XBRL (eXtensible Business Reporting Language) is an XML-based global standard for tagging and exchanging business and financial data in a structured, machine-readable format.
-
B.
XLink
XLink is an XML standard that extends basic linking capabilities by enabling rich, multidirectional, and metadata-enhanced hyperlinks between resources.
-
C.
ELink
ELink is an NCBI E-utilities tool that retrieves and navigates links between related records across NCBI databases.
-
D.
Fieldlink
Fieldlink was an early digital payments and security startup co-founded by Max Levchin that later evolved into the company behind PayPal.
-
E.
XML Base
XML Base is a W3C specification that defines a way to establish base URIs in XML documents so that relative URIs can be resolved consistently.
- 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_69e0b4cc69f481908e98751e697b9df4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2b2d5688190aaa58a2594d4787c |
completed | April 21, 2026, 12:20 a.m. |
Created at: April 16, 2026, 12:39 p.m.