Triple

T3307706
Position Surface form Disambiguated ID Type / Status
Subject Garter motto "Honi soit qui mal y pense" E69489 entity
Predicate associatedOrderFoundedIn P47947 FINISHED
Object 1348 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: 1348 | Statement: [Garter motto "Honi soit qui mal y pense", associatedOrderFoundedIn, 1348]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: associatedOrderFoundedIn
Context triple: [Garter motto "Honi soit qui mal y pense", associatedOrderFoundedIn, 1348]
  • A. orderFoundedIn
    Indicates the place or location where an order (such as a religious, military, or organizational order) was originally established or founded.
  • B. orderFoundedBy
    Indicates that a particular order or organization was established or created by a specific person or entity.
  • C. orderFoundedFrom
    Indicates that an order was initiated or created as a result of, or originating from, a specific source or prior entity.
  • D. foundingOrder
    Indicates the chronological sequence in which entities were founded relative to one another.
  • E. allegedlyOrderedBy
    Indicates that one entity is claimed or reported, but not proven, to have given an order for an action or event involving 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_69ad859f218081909458d2cebbf57565 completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb0cc15088190b51c311c6590df04 completed March 8, 2026, 5:24 p.m.
PD Predicate disambiguation batch_69ada4282730819092aa39c5f9269df0 completed March 8, 2026, 4:30 p.m.
PDg Predicate description generation batch_69ada526764881908e4bd52938d5374d completed March 8, 2026, 4:34 p.m.
Created at: March 8, 2026, 3:11 p.m.