Triple

T33433436
Position Surface form Disambiguated ID Type / Status
Subject Same-Origin Policy E856188 entity
Predicate treatsAsCrossOrigin P179866 FINISHED
Object documents with different scheme 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: documents with different scheme | Statement: [Same-Origin Policy, treatsAsCrossOrigin, documents with different scheme]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: treatsAsCrossOrigin
Context triple: [Same-Origin Policy, treatsAsCrossOrigin, documents with different scheme]
  • A. supportsCrossSiteRequests
    Indicates that an entity allows or is compatible with making requests across different domains or origins.
  • B. originProtectedStatus
    Indicates that an entity’s original source or location is subject to protection, restriction, or special safeguarding status.
  • C. originPolicy
    Indicates the rule or principle that governs how something originates from, is derived from, or is associated with a particular source or starting point.
  • D. isCrossBorder
    Indicates that the relationship or action involves entities located in or spanning across different national or jurisdictional boundaries.
  • E. hasTypeOfCross
    Indicates that an entity possesses or is associated with a specific type or style of cross.
  • F. None of above. chosen

Provenance (4 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_69f727afd5d88190ad48735cd1b32787 completed May 3, 2026, 10:47 a.m.
PD Predicate disambiguation batch_69f72737c42c8190a3f781a5e98868ff completed May 3, 2026, 10:45 a.m.
PDg Predicate description generation batch_69f727ad9ff88190ba8069dd48b2e98f completed May 3, 2026, 10:47 a.m.
Created at: May 1, 2026, 1:36 a.m.