Triple

T6999790
Position Surface form Disambiguated ID Type / Status
Subject Regent of the Kingdom of Hungary E162305 entity
Predicate wasInForceDuring P73498 FINISHED
Object interwar period in Hungary 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: interwar period in Hungary | Statement: [Regent of the Kingdom of Hungary, wasInForceDuring, interwar period in Hungary]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wasInForceDuring
Context triple: [Regent of the Kingdom of Hungary, wasInForceDuring, interwar period in Hungary]
  • A. enactedDuring
    Indicates that an action, event, or state occurred within the temporal span of a specified time period or event.
  • B. inForceSince
    Indicates that a rule, law, agreement, or condition has been officially in effect starting from a specified date or time.
  • C. remainedInForceUntil
    Indicates that a rule, condition, or state continued to be valid or effective up to a specified point in time.
  • D. cameIntoForceInYear
    Indicates that a law, agreement, or formal measure became legally effective or operational in a specified calendar year.
  • E. livedDuring
    Indicates that the subject existed or was alive at some point within the time period or lifespan associated with the object.
  • 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_69c68857ffc08190857dc62cd5253777 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6dc0e54c88190b092870f2d128510 completed March 27, 2026, 7:35 p.m.
PD Predicate disambiguation batch_69c6d7c67c94819084fdcf0398606027 completed March 27, 2026, 7:17 p.m.
PDg Predicate description generation batch_69c6d8c575f081908b43d95d1d99b1a4 completed March 27, 2026, 7:21 p.m.
Created at: March 27, 2026, 2:33 p.m.