Triple

T5593074
Position Surface form Disambiguated ID Type / Status
Subject Patpatar E146927 entity
Predicate hasAlternativeName P39 FINISHED
Object Patpatar-Kara E146927 NE 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: Patpatar-Kara | Statement: [Patpatar, hasAlternativeName, Patpatar-Kara]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Patpatar-Kara
Context triple: [Patpatar, hasAlternativeName, Patpatar-Kara]
  • A. Patpatar chosen
    Patpatar is an Austronesian language spoken in parts of New Ireland in Papua New Guinea, belonging to the Meso-Melanesian subgroup.
  • B. Patrae
    Patrae, also known as Patras, is an ancient and modern port city in the northern Peloponnese of Greece that has long served as a major commercial and cultural center in the region.
  • C. Patigi
    Patigi is a town and local government area in central Nigeria known for its Nupe cultural heritage and proximity to the River Niger.
  • D. Pekat
    Pekat is a settlement on the Indonesian island of Sumbawa that was devastated by the catastrophic 1815 eruption of Mount Tambora.
  • E. Karo
    Karo is a Jewish family name most famously associated with Rabbi Yosef Karo, the 16th-century author of the Shulchan Aruch.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69c009036c408190981a8d690b679b67 completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c020bb08648190ab1f66cc3e897e6d completed March 22, 2026, 5:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0286b4d2c8190a3224f3082316dc8 completed March 22, 2026, 5:35 p.m.
Created at: March 22, 2026, 3:38 p.m.