Triple

T211467
Position Surface form Disambiguated ID Type / Status
Subject Commission for Confidential Matters E4727 entity
Predicate governsDomain P760 FINISHED
Object confidential curial affairs 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: confidential curial affairs | Statement: [Commission for Confidential Matters, governsDomain, confidential curial affairs]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: governsDomain
Context triple: [Commission for Confidential Matters, governsDomain, confidential curial affairs]
  • A. regulatoryDomain
    Indicates that one entity defines or governs the rules, policies, or constraints under which another entity must operate.
  • B. governs chosen
    Indicates that one entity exercises authoritative control, direction, or rule over another entity or domain.
  • C. policyDomain
    Indicates the thematic or subject-matter area to which a given policy, rule, or regulatory action belongs.
  • D. governedFrom
    Indicates that an entity exercises governing authority or administrative control over another entity from a specific location or seat of power.
  • E. governedAs
    Indicates that one entity exercises authoritative control, direction, or rule over another according to some system of governance or leadership.
  • 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_69a2575cb1dc8190a01ad332426dc339 completed Feb. 28, 2026, 2:47 a.m.
NER Named-entity recognition batch_69a25d35aa288190966b6e15af1525cb completed Feb. 28, 2026, 3:12 a.m.
PD Predicate disambiguation batch_69a25b4f71b88190866c8262922ae204 completed Feb. 28, 2026, 3:04 a.m.
Created at: Feb. 28, 2026, 2:52 a.m.