Triple

T1591572
Position Surface form Disambiguated ID Type / Status
Subject UN Security Council Resolution 1368 E34187 entity
Predicate bodyOfLaw P6527 FINISHED
Object international 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: international law | Statement: [UN Security Council Resolution 1368, bodyOfLaw, international law]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: bodyOfLaw
Context triple: [UN Security Council Resolution 1368, bodyOfLaw, international law]
  • A. branchOfLaw
    Indicates a relationship where one legal field or discipline is a subdivision or specialized area within a broader body of law.
  • B. legalDoctrine
    Indicates that one legal principle, rule, or theory is being applied, referenced, or relied upon as an authoritative basis for interpreting or deciding a legal issue.
  • C. legalSystem
    Indicates the formal framework of laws, rules, and institutions that governs how legal matters are defined, interpreted, and enforced within a society or jurisdiction.
  • D. typeOfLaw chosen
    Indicates that one entity is a specific category or kind of law to which the other entity pertains.
  • E. lawJournal
    Indicates a relationship where a work is published in, associated with, or appears within a specific law journal.
  • 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_69a885fceb2c8190b47e0f7c0aefbff0 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a93aedd45c819085843ac843d640e8 completed March 5, 2026, 8:12 a.m.
PD Predicate disambiguation batch_69a907bdc19081908c84c5c0aa09e282 completed March 5, 2026, 4:34 a.m.
Created at: March 4, 2026, 7:27 p.m.