Triple

T8266231
Position Surface form Disambiguated ID Type / Status
Subject Hittite laws E193307 entity
Predicate containsRegulationsOn P34675 FINISHED
Object property law 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: property law | Statement: [Hittite laws, containsRegulationsOn, property law]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: containsRegulationsOn
Context triple: [Hittite laws, containsRegulationsOn, property law]
  • A. hasRegulations chosen
    Indicates that one entity imposes, contains, or is associated with rules or regulatory requirements that govern the behavior or operation of another entity.
  • B. subjectToRegulation
    Indicates that an entity is governed, constrained, or controlled by a specific rule, law, or regulatory framework.
  • C. relatedRegulation
    Indicates that there exists a regulatory rule, law, or directive that is associated with, governs, or is otherwise relevant to the referenced entity or activity.
  • D. associatedWithRegulation
    Indicates a relationship where something is linked to, governed by, or relevant to a specific regulation or regulatory framework.
  • E. supportsRegulation
    Indicates that one entity endorses, backs, or advocates for the implementation or continuation of a specific regulation.
  • 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_69ca82e081d48190986beaa51f498ab9 completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb794e6880819084dff5df42332835 completed March 31, 2026, 7:35 a.m.
PD Predicate disambiguation batch_69cb36b8707881909aca349230495a5a completed March 31, 2026, 2:51 a.m.
Created at: March 30, 2026, 5:50 p.m.