Triple

T17367628
Position Surface form Disambiguated ID Type / Status
Subject Karawang E422224 entity
Predicate locatedNear P294 FINISHED
Object Cikarang 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: Cikarang | Statement: [Karawang, locatedNear, Cikarang]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cikarang
Context triple: [Karawang, locatedNear, Cikarang]
  • A. Bekasi chosen
    Bekasi is a large, rapidly growing industrial and residential city in the Greater Jakarta metropolitan area of Indonesia.
  • B. Depok
    Depok is a rapidly growing commuter city in Indonesia located between Jakarta and Bogor, known for its universities and residential developments.
  • C. Cipatat
    Cipatat is a district-level administrative area located within West Bandung Regency in West Java, Indonesia.
  • D. Bogor Regency
    Bogor Regency is an administrative region in West Java, Indonesia, that encircles the city of Bogor and is known for its rapidly growing suburban and rural communities.
  • E. Bogor
    Bogor is a city on the Indonesian island of Java known for its cool climate, botanical gardens, and role as a major educational and research center.
  • 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_69d889d6535c81908be333c01deaec4e completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e43a661fc08190a4c386125bddb16b completed April 19, 2026, 2:13 a.m.
Created at: April 10, 2026, 5:44 a.m.