Triple

T11700696
Position Surface form Disambiguated ID Type / Status
Subject cross pattée E278115 entity
Predicate hasNotableUseExample P101325 FINISHED
Object basis for the design of the Prussian Iron Cross 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: basis for the design of the Prussian Iron Cross | Statement: [cross pattée, hasNotableUseExample, basis for the design of the Prussian Iron Cross]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNotableUseExample
Context triple: [cross pattée, hasNotableUseExample, basis for the design of the Prussian Iron Cross]
  • A. hasNotableFeature
    Indicates that an entity possesses a specific characteristic, trait, or attribute that is considered significant or noteworthy.
  • B. hasNonExample
    Indicates that something is associated with an instance that explicitly does not satisfy or illustrate a given concept, rule, or category.
  • C. doesNotUse
    Indicates that one entity intentionally refrains from employing, utilizing, or relying on another entity, method, or resource.
  • D. notAutomaticallyUsedBy
    Indicates that something is not used by another entity in an automatic or default manner and instead requires explicit action or configuration to be used.
  • E. canBeUsedWithout
    Indicates that one entity is capable of functioning or being utilized independently of another specified 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_69d6aafe02d881909900d54ad7d4af84 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a49a025881909377c81d3debf465 completed April 10, 2026, 7:19 a.m.
PD Predicate disambiguation batch_69d88a7b30948190b616a9db5c5488d5 completed April 10, 2026, 5:28 a.m.
PDg Predicate description generation batch_69d89546a8688190b51455b5e12caf91 completed April 10, 2026, 6:14 a.m.
Created at: April 8, 2026, 9:40 p.m.