Triple

T23082732
Position Surface form Disambiguated ID Type / Status
Subject Støren E575518 entity
Predicate hasNearbyVillage P4647 FINISHED
Object Lundamo 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: Lundamo | Statement: [Støren, hasNearbyVillage, Lundamo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lundamo
Context triple: [Støren, hasNearbyVillage, Lundamo]
  • A. Lundamo chosen
    Lundamo is a small village in Trøndelag county, Norway, situated within the municipality of Melhus.
  • B. Domaso
    Domaso is a picturesque lakeside town on the northern shore of Lake Como in Italy, known for its waterfront promenades, water sports, and scenic mountain backdrop.
  • C. Mundlana
    Mundlana is a town located in the Sonipat district of the northern Indian state of Haryana.
  • D. Luman
    Luman is a masculine given name of English origin, historically borne by figures such as the 19th-century American art patron Luman Reed.
  • E. Lobata
    Lobata is an administrative district on the island of São Tomé in the central African island nation of São Tomé and Príncipe.
  • 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_69e245bf3e3c819086d3448720efc01b completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f18da239e48190ad041261c6b510a0 completed April 29, 2026, 4:48 a.m.
Created at: April 17, 2026, 3:56 p.m.