Triple
T23312938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ebXML |
E590629
|
entity |
| Predicate | uses |
P98
|
FINISHED |
| Object | SOAP |
—
|
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: SOAP | Statement: [ebXML, uses, SOAP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SOAP Context triple: [ebXML, uses, SOAP]
-
A.
SOAP API
A SOAP API is a web service interface that uses the SOAP protocol to enable structured, standards-based communication between applications over a network.
-
B.
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.
-
C.
W3C SOAP specification
chosen
The W3C SOAP specification is a World Wide Web Consortium standard that defines a protocol for exchanging structured information in web services using XML-based messaging.
-
D.
XML-RPC
XML-RPC is a simple, XML-based remote procedure call protocol that allows software running on different operating systems and in different environments to make procedure calls over HTTP.
-
E.
USOAP
USOAP is an ICAO program that systematically audits and monitors countries’ civil aviation safety oversight systems to ensure compliance with international standards.
- 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_69e25d1d32188190948eb76909d1dcc3 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1972ca70481909e2415c65964210a |
completed | April 29, 2026, 5:29 a.m. |
Created at: April 17, 2026, 5:06 p.m.