Triple

T7898806
Position Surface form Disambiguated ID Type / Status
Subject Regulation (EU) 2018/1139 E183397 entity
Predicate adoptionProcedure P7523 FINISHED
Object ordinary legislative procedure 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: ordinary legislative procedure | Statement: [Regulation (EU) 2018/1139, adoptionProcedure, ordinary legislative procedure]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: adoptionProcedure
Context triple: [Regulation (EU) 2018/1139, adoptionProcedure, ordinary legislative procedure]
  • A. adoption
    Indicates the legal or formal act by which one party assumes parental or custodial responsibility for another, typically a child, creating a recognized parent–child relationship.
  • B. adoptionRequires
    Indicates that one action, condition, or entity must be in place as a prerequisite for an adoption to occur or be valid.
  • C. adoptionResult
    Indicates the outcome or status resulting from an adoption process between entities.
  • D. adoptionStatus
    Indicates the current state or outcome of an adoption relationship or process between entities.
  • E. adoptedThrough chosen
    Indicates that an adoption relationship was established or carried out by means of a specified process, channel, or intermediary.
  • 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_69ca828d13088190b222be7aa9f9315c completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3a2ae5048190a6824d34b582c366 completed March 31, 2026, 3:06 a.m.
PD Predicate disambiguation batch_69cae92d94448190b4425bbfb64c658c completed March 30, 2026, 9:20 p.m.
Created at: March 30, 2026, 5:01 p.m.