Triple

T17036839
Position Surface form Disambiguated ID Type / Status
Subject Tunggul Ametung E413341 entity
Predicate associatedWith P37 FINISHED
Object Tumapel E1245979 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: Tumapel | Statement: [Tunggul Ametung, associatedWith, Tumapel]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tumapel
Context triple: [Tunggul Ametung, associatedWith, Tumapel]
  • A. Tumapel chosen
    Tumapel was an early Javanese polity and settlement in East Java, historically associated with Ken Angrok and the rise of the Singhasari kingdom.
  • B. Tamasopo
    Tamasopo is a small town in the Huasteca Potosina region of San Luis Potosí, Mexico, known for its lush landscapes and popular nearby waterfalls and natural swimming areas.
  • C. Tumeremo
    Tumeremo is a mining town in southeastern Venezuela known for its gold deposits and location within Bolívar State.
  • D. Takudh
    Takudh is an alternative name for the Gwich’in language, an Athabaskan language spoken by the Gwich’in people of northwestern Canada and northeastern Alaska.
  • E. Teguima
    Teguima is a dialect of the Opata language historically spoken by an Indigenous group in what is now northern Mexico.
  • 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_69d886cd18288190b006abab23f811b7 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3d8f38b58819093af4054c3459726 completed April 18, 2026, 7:18 p.m.
NED1 Entity disambiguation (via context triple) batch_6a012ed2ad708190a250762997611569 completed May 11, 2026, 1:20 a.m.
Created at: April 10, 2026, 5:33 a.m.