Triple

T37781818
Position Surface form Disambiguated ID Type / Status
Subject Árva E941850 entity
Predicate administrativeCenterHistoric P80438 FINISHED
Object Oravský Podzámok 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: Oravský Podzámok | Statement: [Árva, administrativeCenterHistoric, Oravský Podzámok]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: administrativeCenterHistoric
Context triple: [Árva, administrativeCenterHistoric, Oravský Podzámok]
  • A. historicAdministrativeCentre chosen
    Indicates that a place served as the main administrative or governmental center for a region or jurisdiction during a past historical period.
  • B. historicalCenterFor
    Indicates that one entity has served as a central or focal place of historical significance, activity, or development for another entity.
  • C. hasHistoricCenterStatus
    Indicates that an entity has been designated or recognized as a historic center, typically due to its cultural, architectural, or historical significance.
  • D. historicallyImportantCenter
    Indicates that a place has served as a significant focal point of historical events, activities, or influence.
  • E. hasHistoricCenterNearby
    Indicates that one entity is located close to another entity that serves as a historic center or historically significant core area.
  • 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_69f76ee5cb0c81909a363d1c929156c0 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fe86cad5108190b0164b8bc6fc23ea completed May 9, 2026, 12:58 a.m.
PD Predicate disambiguation batch_69fe83c0c9888190b6fc40c7f727b569 completed May 9, 2026, 12:45 a.m.
Created at: May 3, 2026, 4:19 p.m.