Triple

T15083636
Position Surface form Disambiguated ID Type / Status
Subject King of Etruria E360212 entity
Predicate hasStyle P1609 FINISHED
Object His Majesty E4827 NE 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: His Majesty | Statement: [King of Etruria, hasStyle, His Majesty]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: His Majesty
Context triple: [King of Etruria, hasStyle, His Majesty]
  • A. His Majesty chosen
    His Majesty is the formal style of address used for a reigning male British monarch.
  • B. His Royal Majesty
    His Royal Majesty is a formal royal style traditionally used to address or refer to a reigning king with the highest honor and dignity.
  • C. Your Majesty
    "Your Majesty" is a formal style of address used when speaking directly to a reigning king or queen.
  • D. His Majesty the King
    His Majesty the King is the formal royal style used to address and refer to the reigning monarch of Thailand.
  • E. His Majesty the King
    His Majesty the King is the formal royal style used to address Gustav III, the 18th-century King of Sweden known for his enlightened absolutism and cultural patronage.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d85a035aa88190b52a139d3a1b7b6d completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e0027450a48190a84588b6aaf84ebf completed April 15, 2026, 9:26 p.m.
NED1 Entity disambiguation (via context triple) batch_69feae179a24819097019976707c93e1 completed May 9, 2026, 3:46 a.m.
Created at: April 10, 2026, 3:03 a.m.