Triple
T33433442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Same-Origin Policy |
E856188
|
entity |
| Predicate | hasExceptionMechanism |
P169927
|
FINISHED |
| Object | CORS |
—
|
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: CORS | Statement: [Same-Origin Policy, hasExceptionMechanism, CORS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExceptionMechanism Context triple: [Same-Origin Policy, hasExceptionMechanism, CORS]
-
A.
hasMechanism
Indicates that one entity operates, functions, or produces an effect through the specified mechanism or process.
-
B.
hasEnforcementMethod
chosen
Indicates that an entity applies, uses, or is associated with a specific method or mechanism for enforcing rules, obligations, or constraints.
-
C.
haveExceptionMember
Indicates that an entity includes or is associated with a member that represents an exception to a rule, condition, or normal behavior.
-
D.
haveHighLevelMechanism
Indicates that an entity possesses or is associated with a high-level, abstract mechanism explaining how something works or occurs.
-
E.
hasException
Indicates that a general rule, process, or condition does not apply in a particular case due to a specified exception.
- 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_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 1, 2026, 1:36 a.m.