Triple

T3055952
Position Surface form Disambiguated ID Type / Status
Subject French customs authorities E60480 entity
Predicate usesLegalBasis P125 FINISHED
Object French customs law 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: French customs law | Statement: [French customs authorities, usesLegalBasis, French customs law]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesLegalBasis
Context triple: [French customs authorities, usesLegalBasis, French customs law]
  • A. legalBasis chosen
    Indicates the legal rule, authority, or justification under which an action, decision, or status is established or carried out.
  • B. usesLegalCode
    Indicates that one entity applies, references, or operates under a particular legal code in its actions or regulations.
  • C. hasLegalSubject
    Indicates that an entity serves as the legal subject (e.g., rights-holder or obligated party) in a legal relationship or context.
  • D. hasLegalRight
    Indicates that an entity possesses an officially recognized legal entitlement or permission to perform an action or hold a claim regarding another entity.
  • E. legalBasisForExecution
    Indicates that one entity serves as the legal justification or authority for carrying out the execution of another entity or action.
  • 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_69ad8578137c81908259dcb27c7d6d7c completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ad9bf7ebd48190ad5748a18fa9a56a completed March 8, 2026, 3:55 p.m.
PD Predicate disambiguation batch_69ad962326e081909d5521c3d3ea3158 completed March 8, 2026, 3:30 p.m.
Created at: March 8, 2026, 3:02 p.m.