Triple

T14359637
Position Surface form Disambiguated ID Type / Status
Subject Moropant Tambe E356062 entity
Predicate familyName P18 FINISHED
Object Tambe E356062 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: Tambe | Statement: [Moropant Tambe, familyName, Tambe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tambe
Context triple: [Moropant Tambe, familyName, Tambe]
  • A. Tambe chosen
    Tambe is an Indian surname, notably borne by figures such as Moropant Tambe, associated with the Maratha and broader Maharashtrian communities.
  • B. Taburao
    Taburao is a village on the atoll of Abaiang in the island nation of Kiribati.
  • C. Takaishi
    Takaishi is a city in Osaka Prefecture, Japan, known as a small industrial and residential hub within the Osaka metropolitan area.
  • D. Shimamoto
    Shimamoto is a town in Osaka Prefecture, Japan, located between Kyoto and Osaka along the Yodo River.
  • E. Kamikawa
    Kamikawa is a town in Hokkaido, Japan, known as a gateway to the mountainous landscapes and hot springs of Daisetsuzan National Park.
  • 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_69d82790a7e08190877e2d349b2e8d8e completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de8f54bfb08190a27c0d12731acec2 completed April 14, 2026, 7:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd4c48dd408190ac45ad4ca6f610c3 completed May 8, 2026, 2:36 a.m.
Created at: April 10, 2026, 1:15 a.m.