Triple

T6836735
Position Surface form Disambiguated ID Type / Status
Subject Avon Valley Line E157468 entity
Predicate connects P390 FINISHED
Object Avonmouth E231309 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: Avonmouth | Statement: [Avon Valley Line, connects, Avonmouth]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Avonmouth
Context triple: [Avon Valley Line, connects, Avonmouth]
  • A. Avonmouth chosen
    Avonmouth is a port and industrial district on the Severn Estuary near Bristol in southwest England.
  • B. Nailsea
    Nailsea is a small town in North Somerset, England, historically known for its glassmaking and coal mining industries.
  • C. Clevedon
    Clevedon is a coastal town in southwest England known for its Victorian pier and views across the Severn Estuary.
  • D. Coalport
    Coalport is a historic village in Shropshire, England, best known for its former porcelain works and role in the early Industrial Revolution within the Ironbridge Gorge.
  • E. Crich
    Crich is a village in Derbyshire, England, known for its historic tramway museum and scenic location on the edge of the Peak District.
  • 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_69c6882c53608190b99aebef079b23bd completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d67c1c508190ab39b8aaaaacc628 completed March 27, 2026, 7:11 p.m.
NED1 Entity disambiguation (via context triple) batch_69c723ffce448190ac8edbaaa1517972 completed March 28, 2026, 12:42 a.m.
Created at: March 27, 2026, 2:19 p.m.