Triple
T33433380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Access-Control-Allow-Methods |
E856187
|
entity |
| Predicate | sentInResponseTo |
P767
|
FINISHED |
| Object | CORS preflight request |
—
|
LITERAL 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: CORS preflight request | Statement: [Access-Control-Allow-Methods, sentInResponseTo, CORS preflight request]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sentInResponseTo Context triple: [Access-Control-Allow-Methods, sentInResponseTo, CORS preflight request]
-
A.
wasResponseTo
chosen
Indicates that one event, action, or communication occurred as a direct reply or reaction to a preceding event, action, or communication.
-
B.
sentIn
Indicates that something (such as a message, document, or item) was transmitted or dispatched to a recipient or destination at a particular time or via a particular medium.
-
C.
sentAs
Indicates that one entity was transmitted, dispatched, or delivered in the form, role, or capacity of another (e.g., an item or message being sent as something specific).
-
D.
responseFrom
Indicates that one entity is the originator or source of a response directed to another entity or request.
-
E.
sentAgainst
Indicates that something (such as a message, request, or action) is directed or dispatched in opposition to a particular target or entity.
- F. None of above.
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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:36 a.m.