Triple

T5559088
Position Surface form Disambiguated ID Type / Status
Subject United Nations Office of Legal Affairs E145719 entity
Predicate hasWorkArea P64475 FINISHED
Object international humanitarian 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 humanitarian law | Statement: [United Nations Office of Legal Affairs, hasWorkArea, international humanitarian law]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasWorkArea
Context triple: [United Nations Office of Legal Affairs, hasWorkArea, international humanitarian law]
  • A. hasCoreArea
    Indicates that an entity possesses a primary or central area that is fundamental to its structure, function, or focus.
  • B. hasWaitingArea
    Indicates that an entity provides or includes a designated space where people can wait before receiving a service or proceeding to another area.
  • C. hasWorkingMode
    Indicates that an entity operates under or supports a particular mode or configuration of functioning.
  • D. hasAreaRange
    Indicates that something’s area falls within a specified minimum-to-maximum range.
  • E. hasPortArea
    Indicates that an entity possesses or is associated with a specific port area, typically representing the spatial extent or boundary of its port facilities.
  • 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_69c008fcaf788190bafa02a1917ee73b completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c020167afc8190b0c518907cd0d99b completed March 22, 2026, 5 p.m.
PD Predicate disambiguation batch_69c01b10bbf8819098655839c03b7832 completed March 22, 2026, 4:38 p.m.
PDg Predicate description generation batch_69c01f0684908190ae2d14f0bd2ab892 completed March 22, 2026, 4:55 p.m.
Created at: March 22, 2026, 3:36 p.m.