Triple

T5450578
Position Surface form Disambiguated ID Type / Status
Subject Reglamento Provisorio de 1815 E122357 entity
Predicate vigencia P33304 FINISHED
Object aplicación limitada y de corta duración 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: aplicación limitada y de corta duración | Statement: [Reglamento Provisorio de 1815, vigencia, aplicación limitada y de corta duración]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: vigencia
Context triple: [Reglamento Provisorio de 1815, vigencia, aplicación limitada y de corta duración]
  • A. effectiveFor
    Indicates that one entity successfully produces the intended effect, benefit, or desired outcome for another entity or condition.
  • B. validityType
    Indicates the specific kind or category of validity that characterizes how or under what conditions something is considered valid.
  • C. effectiveYear
    Indicates the calendar year in which something (such as a rule, status, or agreement) becomes valid or takes effect.
  • D. validityPeriodForAdults
    Indicates the time span during which something is considered valid or applicable specifically for adults.
  • E. hasValidityPeriod chosen
    Indicates that something is associated with a specific time span during which it is considered valid or in effect.
  • 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_69bd4640f52c81909e653ec361f66d76 completed March 20, 2026, 1:06 p.m.
NER Named-entity recognition batch_69bd95be329c81908783420cf81b6af5 completed March 20, 2026, 6:45 p.m.
PD Predicate disambiguation batch_69bd919e8d18819098c4af6a015e5cc2 completed March 20, 2026, 6:27 p.m.
Created at: March 20, 2026, 2:07 p.m.