Triple

T929837
Position Surface form Disambiguated ID Type / Status
Subject Red Cross emblem E20064 entity
Predicate designSpecifiedBy P21520 FINISHED
Object international humanitarian law treaties 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 treaties | Statement: [Red Cross emblem, designSpecifiedBy, international humanitarian law treaties]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: designSpecifiedBy
Context triple: [Red Cross emblem, designSpecifiedBy, international humanitarian law treaties]
  • A. isDesignedAs
    Indicates that something has been intentionally created or configured to serve as or function in the role of something else.
  • B. isDesignedFor
    Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
  • C. designedBy
    Indicates that one entity is the creator, planner, or architect responsible for the form or structure of another entity.
  • D. designedIn
    Indicates that something was created, planned, or conceived during a particular time period or at a specific location.
  • E. hasDesign
    Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
  • 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_69a493af3dc48190adb7263e6e445ea1 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4b349b3d0819090c58b4fb60c6a1b completed March 1, 2026, 9:44 p.m.
PD Predicate disambiguation batch_69a4b29876348190a29f4ff9878074a5 completed March 1, 2026, 9:41 p.m.
PDg Predicate description generation batch_69a4b2f4e3fc81908c8a2d1fbef9c5d2 completed March 1, 2026, 9:43 p.m.
Created at: March 1, 2026, 7:40 p.m.