Triple

T2715040
Position Surface form Disambiguated ID Type / Status
Subject Imperial China E59947 entity
Predicate usesTitleForRuler P10405 FINISHED
Object emperor 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: emperor | Statement: [Imperial China, usesTitleForRuler, emperor]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesTitleForRuler
Context triple: [Imperial China, usesTitleForRuler, emperor]
  • A. hasRulerTitle
    Indicates that a ruler holds or is associated with a specific formal title of rulership.
  • B. usesTitle chosen
    Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
  • C. isTitleFor
    Indicates that one entity serves as the official title or name designation for another entity.
  • D. namedForTitle
    Indicates that one entity is named after or in honor of the title (such as a rank, honorific, or formal designation) associated with another entity.
  • E. containsTitle
    Indicates that one entity includes or holds another entity’s title as part of its content or metadata.
  • F. None of above.

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_69ab4ac92a088190bc74bca14038e3de completed March 6, 2026, 9:44 p.m.
NER Named-entity recognition batch_69abda93a2388190b55a1c821ef6bc64 completed March 7, 2026, 7:58 a.m.
PD Predicate disambiguation batch_69abd8240920819087a812d816a55edb completed March 7, 2026, 7:47 a.m.
Created at: March 6, 2026, 9:55 p.m.