Triple

T36638035
Position Surface form Disambiguated ID Type / Status
Subject Regulation (EU) No 1077/2011 E904512 entity
Predicate managesSystemViaAgency P109459 FINISHED
Object Schengen Information System (SIS II) 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: Schengen Information System (SIS II) | Statement: [Regulation (EU) No 1077/2011, managesSystemViaAgency, Schengen Information System (SIS II)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: managesSystemViaAgency
Context triple: [Regulation (EU) No 1077/2011, managesSystemViaAgency, Schengen Information System (SIS II)]
  • A. implementedByAgency
    Indicates that an action, program, or policy is carried out or executed by a specific agency.
  • B. managingAgencyAbbreviation
    Indicates that one entity is identified by the abbreviated name of the agency responsible for managing or overseeing it.
  • C. supervisedAgency
    Indicates that one entity oversees, directs, or manages the activities or operations of another agency.
  • D. directsAgency
    Indicates that one entity has the authority or role of directing, managing, or overseeing the operations or activities of an agency.
  • E. managingAgencies chosen
    Indicates that one or more agencies are responsible for overseeing, directing, or administering the entity in question.
  • 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_69f76e6c63e48190b1d0c3a79a6c7406 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fd2cf39b0c8190811b8a6fa9410560 completed May 8, 2026, 12:23 a.m.
PD Predicate disambiguation batch_69fd2ad8dd988190a9899701ba00d917 completed May 8, 2026, 12:14 a.m.
Created at: May 3, 2026, 4:11 p.m.