Triple

T20104895
Position Surface form Disambiguated ID Type / Status
Subject Mughal Subah of Orissa E490141 entity
Predicate hadPort P2745 FINISHED
Object Pipili 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: Pipili | Statement: [Mughal Subah of Orissa, hadPort, Pipili]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pipili
Context triple: [Mughal Subah of Orissa, hadPort, Pipili]
  • A. Pipili chosen
    Pipili is a town in the Indian state of Odisha, noted for its traditional appliqué handicrafts and vibrant textile art.
  • B. Pischa
    Pischa is a mountain area and ski region near Davos in the Swiss Alps, known for its freeride terrain and winter sports opportunities.
  • C. Mampruli
    Mampruli is a Gur language spoken primarily by the Mamprusi people of northern Ghana and neighboring regions.
  • D. Quipile
    Quipile is a rural municipality in the Cundinamarca Department of Colombia, known for its agricultural economy and location in the Andean region.
  • E. Papingo
    Papingo is a picturesque traditional village in the Zagori region of Epirus, northwestern Greece, known for its stone architecture and dramatic mountain scenery.
  • 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_69da62636cc08190982cc71733a17b8d completed April 11, 2026, 3:01 p.m.
NER Named-entity recognition batch_69e666daf73c819089f02ca6faa2c283 completed April 20, 2026, 5:48 p.m.
Created at: April 11, 2026, 11:28 p.m.