Triple

T3511668
Position Surface form Disambiguated ID Type / Status
Subject Xuande Emperor E74207 entity
Predicate numberOfYearReign P22408 FINISHED
Object 10 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: 10 | Statement: [Xuande Emperor, numberOfYearReign, 10]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: numberOfYearReign
Context triple: [Xuande Emperor, numberOfYearReign, 10]
  • A. reignDuration chosen
    Indicates the length of time during which an entity held ruling or governing authority over a domain or group.
  • B. periodOfRule
    Indicates the span of time during which an entity exercised authority, control, or governance over something.
  • C. chronologyWithinReignOf
    Indicates that one event or time period occurs entirely within the span of a specified ruler’s reign.
  • D. dynastyRuled
    Indicates that a particular dynasty held ruling authority or governance over a specified region, state, or people during a certain period.
  • E. adoptedDuringReignOf
    Indicates that one entity (such as a law, policy, or practice) was adopted or came into effect while another entity (typically a ruler or leader) was in power or reigning.
  • 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_69ad85cfb5c881909c9a2edd9d6043cc completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adbc0f6cf8819098a1ec8693cc50e7 completed March 8, 2026, 6:12 p.m.
PD Predicate disambiguation batch_69adae0e770481908528fa35eda53003 completed March 8, 2026, 5:12 p.m.
Created at: March 8, 2026, 3:19 p.m.