Triple
T8755296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XDS |
E208058
|
entity |
| Predicate | usesStandard |
P1587
|
FINISHED |
| Object | ebXML Registry |
E590629
|
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: ebXML Registry | Statement: [XDS, usesStandard, ebXML Registry]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ebXML Registry Context triple: [XDS, usesStandard, ebXML Registry]
-
A.
ebXML
chosen
ebXML (Electronic Business using eXtensible Markup Language) is a modular suite of open standards that enables secure, interoperable electronic business information exchange over the internet.
-
B.
UDDI
UDDI (Universal Description, Discovery, and Integration) is a platform-independent, XML-based registry standard for publishing and discovering web services on the internet.
-
C.
XBRL
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.
-
D.
ESB
ESB is the IATA airport code for Esenboğa International Airport, the main airport serving Ankara, Turkey.
-
E.
WSDL
WSDL (Web Services Description Language) is an XML-based language used to formally describe the interfaces, operations, and message formats of web services so they can be discovered and invoked by clients.
- 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_69ca835cd6b08190bd7c63db92f53c86 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5dd83088819082cf54adc0c04243 |
completed | March 31, 2026, 11:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf43305664819085e762e42b138754 |
completed | April 3, 2026, 4:33 a.m. |
Created at: March 30, 2026, 6:39 p.m.