Triple

T13272620
Position Surface form Disambiguated ID Type / Status
Subject Palu Bay E316101 entity
Predicate hasSettlementOnShore P16159 FINISHED
Object Donggala E390762 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: Donggala | Statement: [Palu Bay, hasSettlementOnShore, Donggala]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Donggala
Context triple: [Palu Bay, hasSettlementOnShore, Donggala]
  • A. Donggala chosen
    Donggala is a coastal town and regency in Indonesia known historically as a key port and administrative center in Central Sulawesi.
  • B. Tidore
    Tidore is an island and historic sultanate in eastern Indonesia that was once a major center of the regional spice trade.
  • C. Tual
    Tual is the main urban and administrative center of the Kai Islands in Indonesia’s Maluku province.
  • D. Ternate
    Ternate is a coastal municipality in the province of Cavite in the Philippines, known for its beaches and historical significance.
  • E. Ternate
    Ternate is a small volcanic island and city in eastern Indonesia that was historically a major center of the global spice trade, especially for cloves.
  • 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_69d806b1d9ac8190852c5571d5bd5f0f completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d99020f710819094c2618662bdc7fd completed April 11, 2026, 12:04 a.m.
NED1 Entity disambiguation (via context triple) batch_69f716cd8c2c8190a28d901fde98dc26 completed May 3, 2026, 9:35 a.m.
Created at: April 9, 2026, 9:26 p.m.