Triple

T33436046
Position Surface form Disambiguated ID Type / Status
Subject HTTP cookie E856240 entity
Predicate crossSiteBehaviorControlledBy P179866 FINISHED
Object SameSite attribute 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: SameSite attribute | Statement: [HTTP cookie, crossSiteBehaviorControlledBy, SameSite attribute]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: crossSiteBehaviorControlledBy
Context triple: [HTTP cookie, crossSiteBehaviorControlledBy, SameSite attribute]
  • A. supportsCrossSiteRequests
    Indicates that an entity allows or is compatible with making requests across different domains or origins.
  • B. crossType
    Indicates a relationship where one entity intersects, passes over, or traverses another, typically implying movement or extension across a boundary, area, or medium.
  • C. treatsAsCrossOrigin chosen
    Indicates that one entity is handled under the rules and restrictions applied to content from a different (cross) origin, rather than as same-origin.
  • D. crossErectedBy
    Indicates that a particular cross was constructed, installed, or set up by a specified agent or entity.
  • E. originProtectedStatus
    Indicates that an entity’s original source or location is subject to protection, restriction, or special safeguarding status.
  • 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_69f7c777e924819081a6634f549fe552 completed May 3, 2026, 10:08 p.m.
PD Predicate disambiguation batch_69f7c475c58c8190a883554231e88c88 completed May 3, 2026, 9:56 p.m.
Created at: May 1, 2026, 1:36 a.m.