Triple

T1967176
Position Surface form Disambiguated ID Type / Status
Subject Palestinian judiciary E42715 entity
Predicate includesLegalFramework P33301 FINISHED
Object civil 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: civil law | Statement: [Palestinian judiciary, includesLegalFramework, civil law]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: includesLegalFramework
Context triple: [Palestinian judiciary, includesLegalFramework, civil law]
  • A. legalBasis
    Indicates the legal rule, authority, or justification under which an action, decision, or status is established or carried out.
  • B. containsLawOn
    Indicates that one entity (such as a document, code, or regulation) includes or sets forth legal provisions concerning another entity or subject.
  • C. usesLegalCode
    Indicates that one entity applies, references, or operates under a particular legal code in its actions or regulations.
  • D. legalRequirement
    Indicates that one entity is obligated by law to perform, provide, or comply with something in relation to another entity or situation.
  • E. relatedLegalSystem
    Indicates that there is an association or connection between two legal systems, such as influence, similarity, shared origin, or mutual relevance.
  • 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_69a88711151c8190940b2572095059d7 completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abb3cf15048190a51f73ed85e1b958 completed March 7, 2026, 5:12 a.m.
PD Predicate disambiguation batch_69abaff7d4a48190ab0d51aefb1c4e31 completed March 7, 2026, 4:56 a.m.
PDg Predicate description generation batch_69abb16a6db48190af04012e8ed2269f completed March 7, 2026, 5:02 a.m.
Created at: March 4, 2026, 7:36 p.m.