Triple

T31137846
Position Surface form Disambiguated ID Type / Status
Subject GS1 DataMatrix E793694 entity
Predicate hasFinderPattern P196628 FINISHED
Object L-shaped solid border 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: L-shaped solid border | Statement: [GS1 DataMatrix, hasFinderPattern, L-shaped solid border]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFinderPattern
Context triple: [GS1 DataMatrix, hasFinderPattern, L-shaped solid border]
  • A. containsFinding
    Indicates that one entity includes, encompasses, or holds a particular finding as part of its content or results.
  • B. hasDiscoveryFeature
    Indicates that an entity includes or supports a capability for discovering, finding, or surfacing other relevant entities, items, or information.
  • C. hasBearingPattern
    Indicates a relationship where an object or system exhibits or is characterized by a specific bearing arrangement or configuration pattern.
  • D. hasPeripheralPattern
    Indicates that one entity exhibits or is characterized by a pattern located at or toward the periphery or outer boundary of another entity.
  • E. hasFindsDisplayedAt
    Indicates that certain discovered items or finds are being shown or exhibited at a particular location or display context.
  • 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_69f224d2b3a48190aa9dd26fbf6eab1a completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69fe5ec9028081909ae3d6fbe2f4cbbc completed May 8, 2026, 10:08 p.m.
PD Predicate disambiguation batch_69fe5e1d715881909fc516fafc707644 completed May 8, 2026, 10:05 p.m.
PDg Predicate description generation batch_69fe5ec84910819094cb15269ace7c51 completed May 8, 2026, 10:08 p.m.
Created at: April 29, 2026, 9:05 p.m.