Triple

T1169390
Position Surface form Disambiguated ID Type / Status
Subject Plegridy E24878 entity
Predicate wasApprovedInEU P807 FINISHED
Object 2014 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: 2014 | Statement: [Plegridy, wasApprovedInEU, 2014]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wasApprovedInEU
Context triple: [Plegridy, wasApprovedInEU, 2014]
  • A. europeanUnionStatus
    Indicates whether an entity is a member of, associated with, or otherwise holds a defined status in relation to the European Union.
  • B. adoptedEuro
    Indicates that a country or entity has officially adopted the euro as its legal currency.
  • C. hasMemberInEEA
    Indicates that an entity has at least one member who is located in, based in, or belongs to the European Economic Area (EEA).
  • D. approvedBy chosen
    Indicates that an action, request, or item has received formal authorization or consent from a specified entity.
  • E. hasCustomsUnion
    Indicates that two or more entities participate in a customs union, sharing a common external tariff and removing customs duties between them.
  • 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_69a494082a7c819095004f423f294a64 completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4bce821b481908bc278a3fa7973f4 completed March 1, 2026, 10:25 p.m.
PD Predicate disambiguation batch_69a4bb5656948190b0b1d5446ad06005 completed March 1, 2026, 10:19 p.m.
Created at: March 1, 2026, 7:45 p.m.