Triple

T21415406
Position Surface form Disambiguated ID Type / Status
Subject Swiss motorway vignette E528287 entity
Predicate requiresProperAffixing P143878 FINISHED
Object true 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: true | Statement: [Swiss motorway vignette, requiresProperAffixing, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: requiresProperAffixing
Context triple: [Swiss motorway vignette, requiresProperAffixing, true]
  • A. hasAffixType
    Indicates that an affix bears a specific morphological type or category within a word-formation process.
  • B. hasPossessiveAffixes
    Indicates that an entity (typically a word or morpheme) carries affixes that mark grammatical possession or ownership.
  • C. requiresProperDispositionFor
    Indicates that one entity must be handled, treated, or disposed of according to specific proper-disposal procedures defined by another entity.
  • D. requiresLeadingIn
    Indicates that one entity must be introduced, prepared, or preceded by another entity or action before it can appropriately occur or be used.
  • E. requiresAlignment
    Indicates that one entity depends on another entity being properly aligned or brought into a specified alignment condition before the relationship or action can occur.
  • F. None of above. chosen

Provenance (4 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_69e0c454c248819093425d1099101c09 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ee62d16bfc8190a1c08dd9d0c80e02 completed April 26, 2026, 7:09 p.m.
PD Predicate disambiguation batch_69e61633f8208190a2a849457c4e4198 completed April 20, 2026, 12:04 p.m.
PDg Predicate description generation batch_69e6190163448190a2404b396215c686 completed April 20, 2026, 12:16 p.m.
Created at: April 16, 2026, 5:45 p.m.