Triple

T10164112
Position Surface form Disambiguated ID Type / Status
Subject Lex Visigothorum E233963 entity
Predicate inForceInPart P92369 FINISHED
Object Christian kingdoms of northern Iberia 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: Christian kingdoms of northern Iberia | Statement: [Lex Visigothorum, inForceInPart, Christian kingdoms of northern Iberia]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: inForceInPart
Context triple: [Lex Visigothorum, inForceInPart, Christian kingdoms of northern Iberia]
  • A. inForceIn
    Indicates that a rule, law, agreement, or condition is currently valid and operative within a specified jurisdiction, context, or time frame.
  • B. inForce
    Indicates that a rule, law, agreement, or condition is currently valid, active, and being applied or enforced.
  • C. inForceAfter
    Indicates that a condition, rule, or agreement becomes valid or operative only after a specified time, event, or state has occurred.
  • D. inForceInPeriod
    Indicates that something (such as a rule, contract, or condition) is valid, applicable, or legally effective during a specified time period.
  • E. inForceUntil
    Indicates that a condition, rule, or agreement remains valid and operative up to a specified time or event.
  • 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_69ca848e80748190b91d1e04d35512c7 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cdec6a7bb48190952f4318af9cc32b completed April 2, 2026, 4:11 a.m.
PD Predicate disambiguation batch_69cd4ba795808190acc9124c98c6e40f completed April 1, 2026, 4:45 p.m.
PDg Predicate description generation batch_69cd4f8f869c8190a82ad040993e0244 completed April 1, 2026, 5:02 p.m.
Created at: March 30, 2026, 9:09 p.m.