Triple

T16808492
Position Surface form Disambiguated ID Type / Status
Subject Royal arms of England within a bordure compony argent and azure E408540 entity
Predicate bordureType P124934 FINISHED
Object bordure compony 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: bordure compony | Statement: [Royal arms of England within a bordure compony argent and azure, bordureType, bordure compony]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: bordureType
Context triple: [Royal arms of England within a bordure compony argent and azure, bordureType, bordure compony]
  • A. sharesBorderType
    Indicates that two entities are connected by a common boundary characterized by the same specified type of border (e.g., land, river, maritime).
  • B. formsPartOfBorderType
    Indicates that one border type constitutes a component or segment of another, more comprehensive border type.
  • C. hadBorderType
    Indicates that a boundary between two entities existed and specifies the nature or classification of that border (e.g., land, maritime, disputed).
  • D. borderColor
    Indicates the color that forms the boundary or outline of an entity.
  • E. typicalBoundary
    Indicates that one entity serves as the usual or characteristic boundary or limit for another entity.
  • 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_69d88393905081908d00a86b99996ac8 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3b2cde590819080dc474292b023ee completed April 18, 2026, 4:35 p.m.
PD Predicate disambiguation batch_69e32b814b188190aee525f8779203cd completed April 18, 2026, 6:58 a.m.
PDg Predicate description generation batch_69e34fb7c8c8819086975b7955b7d8ef completed April 18, 2026, 9:32 a.m.
Created at: April 10, 2026, 5:23 a.m.