Triple

T34211428
Position Surface form Disambiguated ID Type / Status
Subject ministerio de defensa E877666 entity
Predicate puedeEstarSujetoA P1313 FINISHED
Object control parlamentario 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: control parlamentario | Statement: [ministerio de defensa, puedeEstarSujetoA, control parlamentario]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: puedeEstarSujetoA
Context triple: [ministerio de defensa, puedeEstarSujetoA, control parlamentario]
  • A. isSubjectTo chosen
    Indicates that one entity is governed, affected, or constrained by the authority, rules, conditions, or influence of another entity.
  • B. susceptibleTo
    Indicates that one entity is vulnerable or likely to be affected, harmed, or influenced by another entity or factor.
  • C. mayBeSuedUnder
    Indicates that one entity is legally subject to being sued or brought to court under a specified law, statute, or legal framework by another entity.
  • D. canBeSuedFor
    Indicates that one party is legally liable or potentially subject to legal action by another party for a specified cause or wrongdoing.
  • E. hasLegalSubject
    Indicates that an entity serves as the legal subject (e.g., rights-holder or obligated party) in a legal relationship or context.
  • 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_69f349b0b4bc819088c1552424089ee9 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f7234bcaa48190ac970759d34e254a completed May 3, 2026, 10:28 a.m.
PD Predicate disambiguation batch_69f72155c48881909bd40b9aa3febd5a completed May 3, 2026, 10:20 a.m.
Created at: May 1, 2026, 1:55 a.m.