Triple

T33842699
Position Surface form Disambiguated ID Type / Status
Subject Caddiegal E867396 entity
Predicate hasHeritageRecognizedIn P193957 FINISHED
Object Sydney 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: Sydney | Statement: [Caddiegal, hasHeritageRecognizedIn, Sydney]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHeritageRecognizedIn
Context triple: [Caddiegal, hasHeritageRecognizedIn, Sydney]
  • A. culturalHeritageRecognizedBy
    Indicates that an entity’s cultural heritage status has been formally acknowledged or designated by a specific recognizing authority or organization.
  • B. hasWorldHeritageSite
    Indicates that a location or entity possesses or contains a site designated as a UNESCO World Heritage Site.
  • C. unescoDesignation
    Indicates that an entity has been granted a specific designation or status by UNESCO.
  • D. hasCulturalHeritageOn
    Indicates that one entity possesses, preserves, or is associated with the cultural heritage embodied in another entity.
  • E. hasWorldHeritageContext
    Indicates that something is associated with, relevant to, or situated within the context of a UNESCO World Heritage site or designation.
  • 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_69f34992ad40819087760ed939bd2a7a completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69fd5bf69acc819092a01e4259785dc3 completed May 8, 2026, 3:43 a.m.
PD Predicate disambiguation batch_69fd59b3f4ac8190a7f9dd3142da6e09 completed May 8, 2026, 3:34 a.m.
PDg Predicate description generation batch_69fd5bf49288819098a12202411cba4f completed May 8, 2026, 3:43 a.m.
Created at: May 1, 2026, 1:47 a.m.