Triple

T21917393
Position Surface form Disambiguated ID Type / Status
Subject Parbate E541214 entity
Predicate historicalNameUsedIn P145623 FINISHED
Object Nepalese court and administration 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: Nepalese court and administration | Statement: [Parbate, historicalNameUsedIn, Nepalese court and administration]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalNameUsedIn
Context triple: [Parbate, historicalNameUsedIn, Nepalese court and administration]
  • A. historicalNameGivenBy
    Indicates that one entity is the name historically assigned to another entity by a specific source, culture, or period.
  • B. historicalNameType
    Indicates that the relationship specifies the type or category of a historical name associated with an entity.
  • C. historicalNameInEnglish
    Indicates that an entity is associated with a historical English-language name by which it was known in the past.
  • D. historicalNameUsedInItaly
    Indicates that a particular historical name was used within the geographical or cultural context of Italy.
  • E. historicallyRecognizedAs
    Indicates that an entity has been acknowledged or designated under a particular name, status, or role during a past historical period.
  • 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_69e0c47c4b9c8190a5586a75f5f36453 completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f1233858308190a877d8015db4d380 completed April 28, 2026, 9:14 p.m.
PD Predicate disambiguation batch_69e6be9ebf4c8190892df1a8e1313f88 completed April 21, 2026, 12:02 a.m.
PDg Predicate description generation batch_69e6c187bc548190b4ca13150f6bae38 completed April 21, 2026, 12:15 a.m.
Created at: April 16, 2026, 7:43 p.m.