Triple

T12007930
Position Surface form Disambiguated ID Type / Status
Subject Wemyss villages E285830 entity
Predicate hasVillage P4011 FINISHED
Object Methil E9837 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: Methil | Statement: [Wemyss villages, hasVillage, Methil]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Methil
Context triple: [Wemyss villages, hasVillage, Methil]
  • A. Methil chosen
    Methil is a coastal town in eastern Scotland that forms part of the Levenmouth area on the Firth of Forth.
  • B. Southwater
    Southwater is a large village and civil parish in West Sussex, England, situated just south of the town of Horsham.
  • C. River Isbourne
    River Isbourne is a small river in Gloucestershire, England, flowing through the Cotswolds and the town of Winchcombe before joining the River Avon.
  • D. Lysva
    Lysva is an industrial city in Perm Krai, Russia, historically known for its metallurgical and machine-building industries.
  • E. The Nore
    The Nore is a sandbank at the mouth of the Thames Estuary in England that historically served as a major Royal Navy anchorage and site of naval command.
  • 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_69d6ab45a368819084fce08bf0dc3705 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d903d61a4c81909e6cb6500b61df94 completed April 10, 2026, 2:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69f49d32b0608190b261567fbd4f415e completed May 1, 2026, 12:31 p.m.
Created at: April 8, 2026, 9:46 p.m.