Triple

T4327203
Position Surface form Disambiguated ID Type / Status
Subject Financial Services Act 2012 E96660 entity
Predicate regulatoryArchitecture P47143 FINISHED
Object twin peaks model of financial regulation 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: twin peaks model of financial regulation | Statement: [Financial Services Act 2012, regulatoryArchitecture, twin peaks model of financial regulation]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regulatoryArchitecture
Context triple: [Financial Services Act 2012, regulatoryArchitecture, twin peaks model of financial regulation]
  • A. regulatoryStructure chosen
    Indicates a relationship where one entity serves as a regulatory framework, mechanism, or control system that governs, constrains, or modulates the behavior or operation of another entity.
  • B. regulatoryDriver
    Indicates that one entity serves as a motivating or guiding regulatory factor influencing the behavior, decisions, or policies of another entity.
  • C. regulatoryType
    Indicates the specific kind or category of regulatory control, rule, or oversight that applies in the given relationship.
  • D. regulatoryTarget
    Indicates that one entity is subject to control, influence, or governance by another entity under a regulatory or rule-based framework.
  • E. regulatoryOutput
    Indicates that one entity produces or issues a rule, standard, or directive that governs or constrains the behavior of another entity or process.
  • 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_69b34542fd908190b11b08faad8decfd completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b35131f11881909e2d5415a70d5785 completed March 12, 2026, 11:50 p.m.
PD Predicate disambiguation batch_69b34f4e13fc8190a42c519f37959d27 completed March 12, 2026, 11:42 p.m.
Created at: March 12, 2026, 11:13 p.m.