Triple

T26917460
Position Surface form Disambiguated ID Type / Status
Subject Silesian Voivodeship government E677552 entity
Predicate subjectToAuditBy P141871 FINISHED
Object Supreme Audit Office of Poland 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: Supreme Audit Office of Poland | Statement: [Silesian Voivodeship government, subjectToAuditBy, Supreme Audit Office of Poland]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: subjectToAuditBy
Context triple: [Silesian Voivodeship government, subjectToAuditBy, Supreme Audit Office of Poland]
  • A. isSubjectTo
    Indicates that one entity is governed, affected, or constrained by the authority, rules, conditions, or influence of another entity.
  • B. typeOfAudit
    Indicates the specific category or kind of audit being performed or referenced in relation to an entity.
  • C. associatedAuditor chosen
    Indicates that an auditor is linked to, or responsible for auditing, a particular entity or record.
  • D. subjectToReviewProcedure
    Indicates that an entity is required to undergo a formal review process or procedure before a decision, approval, or action is finalized.
  • E. subjectToRegulation
    Indicates that an entity is governed, constrained, or controlled by a specific rule, law, or regulatory framework.
  • 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_69eee9bdebc48190ba90a12a63e09c73 completed April 27, 2026, 4:44 a.m.
NER Named-entity recognition batch_69f68f670b608190a0b6ab60d722b4e0 completed May 2, 2026, 11:57 p.m.
PD Predicate disambiguation batch_69f68b78f29481908cc8f390496dee97 completed May 2, 2026, 11:40 p.m.
Created at: April 27, 2026, 6:05 a.m.