Triple

T17413663
Position Surface form Disambiguated ID Type / Status
Subject East Sepik Province E423431 entity
Predicate hasSettlement P1068 FINISHED
Object Angoram 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: Angoram | Statement: [East Sepik Province, hasSettlement, Angoram]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Angoram
Context triple: [East Sepik Province, hasSettlement, Angoram]
  • A. Angoram chosen
    Angoram is a town in Papua New Guinea known as an important river port and trading center in the Sepik River region.
  • B. Rashua
    Rashua is a small volcanic island in Russia’s Kuril Islands chain in the northwest Pacific Ocean.
  • C. Bangar
    Bangar is a coastal municipality in the province of La Union in the Philippines, known for its handwoven textiles and agricultural products.
  • D. Bogra
    Bogra is a major city and commercial hub in northern Bangladesh, historically part of the Bengal region.
  • E. Oshakan
    Oshakan is a historic village in Armenia renowned as the burial place of Mesrop Mashtots, the creator of the Armenian alphabet, and an important site of Armenian cultural and religious heritage.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d889d7d27c819088486ce3f0627fa1 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e44230fc688190a6a7edc12d9e9947 completed April 19, 2026, 2:47 a.m.
Created at: April 10, 2026, 5:46 a.m.