Triple

T27199708
Position Surface form Disambiguated ID Type / Status
Subject Bonda’ E683700 entity
Predicate spokenInPartOf P162518 FINISHED
Object northern Sulawesi 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: northern Sulawesi | Statement: [Bonda’, spokenInPartOf, northern Sulawesi]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: spokenInPartOf
Context triple: [Bonda’, spokenInPartOf, northern Sulawesi]
  • A. spokenInPartOf chosen
    Indicates that a language or dialect is spoken within a specific subregion or part of a larger geographic or administrative area.
  • B. spokenOfAs
    Indicates that one entity is referred to, characterized, or talked about in a particular way by another entity or within a given context.
  • C. isSpokenAlong
    Indicates that something (typically a language or dialect) is used or spoken in the regions or areas that follow a particular path, boundary, or route.
  • D. possiblySpokenAt
    Indicates that an utterance or speech event may have occurred at a particular time or location, but this association is uncertain or not definitively confirmed.
  • E. spokeAt
    Indicates that a person delivered a talk, speech, or presentation at a particular event or location.
  • 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_69eefad1fd5c8190a4a46ea6afe58bfa completed April 27, 2026, 5:57 a.m.
NER Named-entity recognition batch_69f62cd2ceb481908cd9fae52a542206 completed May 2, 2026, 4:56 p.m.
PD Predicate disambiguation batch_69f62c1762f881908c25e8f70ecd5041 completed May 2, 2026, 4:53 p.m.
Created at: April 27, 2026, 9:35 a.m.