Triple

T5247675
Position Surface form Disambiguated ID Type / Status
Subject the Lawgiver E118504 entity
Predicate associatedWithReign P29663 FINISHED
Object 1520–1566 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: 1520–1566 | Statement: [the Lawgiver, associatedWithReign, 1520–1566]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: associatedWithReign
Context triple: [the Lawgiver, associatedWithReign, 1520–1566]
  • A. correspondsToReignOf chosen
    Indicates that something (such as a time period, event, or record) matches or is associated with the duration of a specific ruler’s reign.
  • B. associatedWithMonarch
    Indicates a relationship where an entity has a connection or affiliation with a monarch, such as through service, governance, lineage, or formal association.
  • C. associatedWithMonarchy
    Indicates a relationship in which something has a connection, link, or relevance to a monarchy or monarchical system.
  • D. associatedWithDynasty
    Indicates that an entity has a historical, political, cultural, or familial connection to a specific dynasty.
  • E. associatedWithEmperor
    Indicates a relationship in which an entity has a connection, link, or affiliation with an emperor, such as through service, influence, kinship, or shared authority.
  • 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_69bd4468aacc8190a8196f71855cdf4f completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd7b77165c8190bd1ce8a197cef226 completed March 20, 2026, 4:53 p.m.
PD Predicate disambiguation batch_69bd77c30bac8190a883ca45da35d667 completed March 20, 2026, 4:37 p.m.
Created at: March 20, 2026, 1:50 p.m.