Triple

T33329747
Position Surface form Disambiguated ID Type / Status
Subject Portuguese heraldry E853369 entity
Predicate usesTincture P188809 FINISHED
Object gules 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: gules | Statement: [Portuguese heraldry, usesTincture, gules]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesTincture
Context triple: [Portuguese heraldry, usesTincture, gules]
  • A. armedTincture
    Indicates that a creature or figure in heraldry is depicted with its claws, talons, or similar natural weapons shown in a specified tincture (color).
  • B. tinctureOrdinary
    Indicates that an ordinary (a basic heraldic shape or charge) is depicted with a specific tincture (color, metal, or fur) in a coat of arms.
  • C. tinctureOfPale
    Indicates that one entity is a tincture (medicinal or alcoholic extract) derived from or characterized by the pale aspect, quality, or component of another entity.
  • D. typicalTincture
    Indicates that something has the usual or standard tincture (coloring or hue) typically associated with it.
  • E. tinctureOfKey
    Indicates that one entity is a tincture (medicinal or alcoholic extract) derived from, containing, or primarily based on another entity designated as the key ingredient.
  • 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_69f34969614c81909cd99661b0902533 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69fbad1e94988190b86d447a68e65067 completed May 6, 2026, 9:05 p.m.
PD Predicate disambiguation batch_69fba881b8e0819094790935152b99a1 completed May 6, 2026, 8:45 p.m.
PDg Predicate description generation batch_69fbad1b3ba08190ad69e21461333f2e completed May 6, 2026, 9:05 p.m.
Created at: May 1, 2026, 1:34 a.m.