Triple

T9075319
Position Surface form Disambiguated ID Type / Status
Subject Sulmo E217468 entity
Predicate hasLatinName P3646 FINISHED
Object Sulmo E217468 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: Sulmo | Statement: [Sulmo, hasLatinName, Sulmo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sulmo
Context triple: [Sulmo, hasLatinName, Sulmo]
  • A. Sulmo chosen
    Sulmo is an ancient town in central Italy, historically known as the birthplace of the Roman poet Ovid.
  • B. Piranga
    Piranga is a genus of brightly colored New World songbirds in the cardinal family, commonly known as tanagers.
  • C. Suau
    Suau is an Oceanic language spoken by communities in southeastern Papua New Guinea, particularly in Milne Bay Province.
  • D. Mahuva
    Mahuva is a coastal town in Gujarat, India, known for its onion production, coconut plantations, and scenic beaches along the Arabian Sea.
  • E. Olema
    Olema is a small unincorporated community in Marin County, California, known as a gateway to Point Reyes National Seashore and the surrounding coastal countryside.
  • 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_69ca83d6c14c8190bc056d927f00a2a2 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cc95c53274819099b3b3047bfe8cc8 completed April 1, 2026, 3:49 a.m.
NED1 Entity disambiguation (via context triple) batch_69d017aea1e481909f329ff451ed941c completed April 3, 2026, 7:40 p.m.
Created at: March 30, 2026, 7:12 p.m.