Triple

T13897849
Position Surface form Disambiguated ID Type / Status
Subject Mona E334135 entity
Predicate near P350 FINISHED
Object Papine E334136 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: Papine | Statement: [Mona, near, Papine]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Papine
Context triple: [Mona, near, Papine]
  • A. Papine chosen
    Papine is a community in the Parish of St. Andrew, Jamaica, known for its proximity to the University of the West Indies and its role as a busy commercial and transportation hub.
  • B. Parnans
    Parnans is a small commune in southeastern France, located in the Drôme department within the Auvergne-Rhône-Alpes region.
  • C. Pacanne
    Pacanne was an 18th-century Miami chief known for his influential leadership and diplomatic role in relations between Native American tribes, European powers, and the emerging United States in the Great Lakes region.
  • D. Tannay
    Tannay is a small lakeside municipality in the canton of Vaud in western Switzerland, situated on the shores of Lake Geneva.
  • E. Pias
    Pias is a civil parish located in the municipality of Serpa in Portugal’s Alentejo region.
  • 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_69d81c5dd2d48190b7a5fc1e009de936 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de25d72c6c819093bf9c43136839d4 completed April 14, 2026, 11:32 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7c720b4988190aee1f1f09877212d completed May 3, 2026, 10:07 p.m.
Created at: April 9, 2026, 10:15 p.m.