Triple
T9898598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OData |
E182234
|
entity |
| Predicate | usesTransport |
P11571
|
FINISHED |
| Object | HTTP |
E1064
|
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: HTTP | Statement: [OData, usesTransport, HTTP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HTTP Context triple: [OData, usesTransport, HTTP]
-
A.
HTTP
chosen
HTTP (Hypertext Transfer Protocol) is the foundational application-layer protocol used for transmitting web pages and other resources across the World Wide Web.
-
B.
HTTP/1.1
HTTP/1.1 is a widely used version of the Hypertext Transfer Protocol that introduced persistent connections, chunked transfer encoding, and improved caching mechanisms for web communication.
-
C.
HTTP/2
HTTP/2 is a major revision of the Hypertext Transfer Protocol that introduced features like multiplexing, header compression, and server push to significantly improve web performance over HTTP/1.1.
-
D.
HAL (Hypertext Application Language)
HAL (Hypertext Application Language) is a simple, JSON-based hypermedia format that standardizes how to represent and navigate links and embedded resources in RESTful APIs.
-
E.
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.
- 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_69ca82876f8081909cf75df0f99bb13f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb4ac27d88190b8255f7e616f95c9 |
completed | April 2, 2026, 12:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1eb17ed548190a2510a667dd988ca |
completed | April 5, 2026, 4:54 a.m. |
Created at: March 30, 2026, 8:40 p.m.