Triple

T19597539
Position Surface form Disambiguated ID Type / Status
Subject Aluva taluk E470385 entity
Predicate containsSettlement P847 FINISHED
Object Nedumbassery 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: Nedumbassery | Statement: [Aluva taluk, containsSettlement, Nedumbassery]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nedumbassery
Context triple: [Aluva taluk, containsSettlement, Nedumbassery]
  • A. Nedumbassery chosen
    Nedumbassery is a suburban area near Kochi in the Indian state of Kerala, best known for hosting Cochin International Airport.
  • B. Ukkadam
    Ukkadam is a prominent commercial and transport hub in Coimbatore, Tamil Nadu, known for its busy markets and connectivity.
  • C. Pattom
    Pattom is a prominent residential and commercial neighborhood in Thiruvananthapuram, Kerala, known for its central location and important institutions.
  • D. Thekkumkur
    Thekkumkur was a small erstwhile kingdom in the Kerala region of South India that later became part of the expanding Travancore state.
  • E. Cheriyam
    Cheriyam is a small island that forms part of the Kalpeni atoll in the Lakshadweep archipelago of India.
  • 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_69d8e510024481908415c0d616fa6186 completed April 10, 2026, 11:54 a.m.
NER Named-entity recognition batch_69e6407b997881909762c8f919c9cdad completed April 20, 2026, 3:04 p.m.
Created at: April 10, 2026, 1:43 p.m.