Triple

T36355331
Position Surface form Disambiguated ID Type / Status
Subject UNESCO World Heritage archaeological sites E895325 entity
Predicate mayBeListedAs P78340 FINISHED
Object World Heritage in Danger NE NERFINISHED

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: World Heritage in Danger | Statement: [UNESCO World Heritage archaeological sites, mayBeListedAs, World Heritage in Danger]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mayBeListedAs
Context triple: [UNESCO World Heritage archaeological sites, mayBeListedAs, World Heritage in Danger]
  • A. isListed chosen
    Indicates that an entity appears on or is included in a specified list, registry, or catalog.
  • B. isListedBy
    Indicates that one entity appears as an item or entry in a list, catalog, or register maintained or provided by another entity.
  • C. listedWith
    Indicates that an entity is included as an item or entry within a particular list, catalog, or collection.
  • D. includesListedOn
    Indicates that one entity contains or references another entity that is recorded or displayed on a specific list or listing.
  • E. listedFor
    Indicates that something has been placed on a list or made available in a catalog, registry, or marketplace for consideration, viewing, or potential selection.
  • 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_69f76e5044248190b390d8887dc03254 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69fcc4b700748190ae00b21d09c96695 completed May 7, 2026, 4:58 p.m.
PD Predicate disambiguation batch_69fcb0f9d3d881908a049475182fb039 completed May 7, 2026, 3:34 p.m.
Created at: May 3, 2026, 4:09 p.m.