Triple
T19998016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frontier |
E494245
|
entity |
| Predicate | supportsProtocol |
P203
|
FINISHED |
| Object | XML-RPC |
—
|
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: XML-RPC | Statement: [Frontier, supportsProtocol, XML-RPC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: XML-RPC Context triple: [Frontier, supportsProtocol, XML-RPC]
-
A.
XML-RPC
chosen
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.
-
B.
XML API
XML API is a legacy HTTP-based interface for interacting with Google Cloud Storage using XML-formatted requests and responses, similar to Amazon S3’s API.
-
C.
RPC
RPC is the commonly used abbreviation for the Dr. Rajendra Prasad Centre for Ophthalmic Sciences, a leading eye care and research institute in India.
-
D.
RPC over HTTP
RPC over HTTP is a Microsoft protocol that allows Remote Procedure Call traffic to be tunneled over HTTP or HTTPS, enabling secure access to services like Exchange over the internet without a traditional VPN.
-
E.
KRPC
KRPC is a major Nigerian oil refinery and petrochemical complex located in Kaduna, involved in processing crude oil into refined petroleum products and petrochemicals.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65fe6827481909469129feb9aad91 |
completed | April 20, 2026, 5:18 p.m. |
Created at: April 11, 2026, 3:32 p.m.