Triple

T38297407
Position Surface form Disambiguated ID Type / Status
Subject Sagrado E1032127 entity
Predicate hasWorldWarIHeritage P112622 FINISHED
Object true 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: true | Statement: [Sagrado, hasWorldWarIHeritage, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasWorldWarIHeritage
Context triple: [Sagrado, hasWorldWarIHeritage, true]
  • A. hasWorldWarIIAssociation
    Indicates that there is a notable connection or relevance between an entity and World War II, such as involvement, impact, or contextual association.
  • B. worldWarIPartOf
    Indicates that an event or entity is a component, phase, or subset of World War I.
  • C. worldWarIService
    Indicates that an entity served or participated in military service during World War I.
  • D. worldWarIRecognition chosen
    Indicates formal acknowledgment or commemoration of involvement, service, or impact related to World War I.
  • E. hasPrimaryTheatreOfWar
    Indicates that an armed conflict or military operation is chiefly conducted within a particular geographic theatre or region of war.
  • 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_69f76e0f2084819091299d021625c3fe completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69fefa064ab48190925759950d0d94d9 completed May 9, 2026, 9:10 a.m.
PD Predicate disambiguation batch_69fef96ae5d08190b027435753c44821 completed May 9, 2026, 9:07 a.m.
Created at: May 3, 2026, 4:30 p.m.