Triple
T10328302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CORS protocol |
E242816
|
entity |
| Predicate | fullName |
P16
|
FINISHED |
| Object | Cross-Origin Resource Sharing |
E242816
|
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: Cross-Origin Resource Sharing | Statement: [CORS protocol, fullName, Cross-Origin Resource Sharing]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cross-Origin Resource Sharing Context triple: [CORS protocol, fullName, Cross-Origin Resource Sharing]
-
A.
CORS processing model
The CORS processing model is the set of rules and algorithms that govern how web browsers handle cross-origin HTTP requests and responses to enforce the Same-Origin Policy while allowing controlled resource sharing.
-
B.
CORS protocol
chosen
The CORS protocol is a web security mechanism that controls how browsers permit cross-origin HTTP requests, enabling safe resource sharing between different domains.
-
C.
CORS network
The CORS network is a nationwide system of continuously operating GPS and GNSS reference stations that provides precise positioning data to support surveying, mapping, and geospatial applications.
-
D.
RFC 7234
RFC 7234 is an IETF specification that defines HTTP/1.1 caching semantics, including how responses may be stored, reused, and validated by caches.
-
E.
RFC 2616
RFC 2616 is the IETF specification that defined HTTP/1.1, standardizing the core semantics and behavior of the Hypertext Transfer Protocol used on the web.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7cf21e08190bf605daeea0d9dcf |
completed | April 7, 2026, 10:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d71db4a8dc81909adb2a044e74fd6b |
completed | April 9, 2026, 3:32 a.m. |
Created at: April 6, 2026, 11:52 a.m.