Triple

T6024608
Position Surface form Disambiguated ID Type / Status
Subject Order of the Elephant E134144 entity
Predicate reestablishedAsRoyalOrder P68815 FINISHED
Object 1693 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: 1693 | Statement: [Order of the Elephant, reestablishedAsRoyalOrder, 1693]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reestablishedAsRoyalOrder
Context triple: [Order of the Elephant, reestablishedAsRoyalOrder, 1693]
  • A. restoredToThroneBy
    Indicates that an entity was returned to a position of rulership or kingship through the actions or intervention of another entity.
  • B. regainsThroneFrom
    Indicates that one entity takes back control of a throne or rulership position that had been held by another entity.
  • C. royalAppointment
    Indicates a formal position, role, or honor that has been officially granted to an entity by a monarch or royal authority.
  • D. habsburgLorraineRuleRestored
    Indicates that political authority or dynastic rule by the House of Habsburg-Lorraine has been re-established after a period of interruption or loss.
  • E. dynastyRestored
    Indicates that a previously displaced ruling dynasty has been returned to power or reestablished as the legitimate authority.
  • 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_69c008742a5c8190b9cb9c2787a3d8b3 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c04fbf048081908b0da0cf838730a5 completed March 22, 2026, 8:23 p.m.
PD Predicate disambiguation batch_69c049e75b3881908be106fbcf8c68d4 completed March 22, 2026, 7:58 p.m.
PDg Predicate description generation batch_69c04e8c5bfc8190b986a7071d1b23e3 completed March 22, 2026, 8:18 p.m.
Created at: March 22, 2026, 4:07 p.m.