Triple

T8272575
Position Surface form Disambiguated ID Type / Status
Subject Camp V E193463 entity
Predicate associatedLegalFramework P61922 FINISHED
Object law of armed conflict 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: law of armed conflict | Statement: [Camp V, associatedLegalFramework, law of armed conflict]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: associatedLegalFramework
Context triple: [Camp V, associatedLegalFramework, law of armed conflict]
  • A. includesLegalFramework
    Indicates that one entity encompasses, references, or incorporates a specific legal framework within its scope or content.
  • B. relatedLegalSystem
    Indicates that there is an association or connection between two legal systems, such as influence, similarity, shared origin, or mutual relevance.
  • C. relatedLegalConcept chosen
    Indicates that one legal concept is connected or associated with another through a relevant legal relationship or context.
  • D. legalBasis
    Indicates the legal rule, authority, or justification under which an action, decision, or status is established or carried out.
  • E. legalAuthorityIn
    Indicates that an entity holds official legal power, jurisdiction, or governing authority within a specified area or domain.
  • 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_69ca82e14ae481908ffdb822cd2192bc completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb798878988190a5f63c854aa070f2 completed March 31, 2026, 7:36 a.m.
PD Predicate disambiguation batch_69cb70a4525481909399d313a6247ace completed March 31, 2026, 6:58 a.m.
Created at: March 30, 2026, 5:50 p.m.