Triple

T31435972
Position Surface form Disambiguated ID Type / Status
Subject Market Harborough Arm of the Grand Union Canal E801929 entity
Predicate hasMooringsAt P76629 FINISHED
Object Market Harborough Basin 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: Market Harborough Basin | Statement: [Market Harborough Arm of the Grand Union Canal, hasMooringsAt, Market Harborough Basin]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMooringsAt
Context triple: [Market Harborough Arm of the Grand Union Canal, hasMooringsAt, Market Harborough Basin]
  • A. mooredAt
    Indicates that one object, typically a vessel or floating structure, is secured or anchored at a specific location or facility.
  • B. hasBoatMoorings chosen
    Indicates that one entity provides or contains designated places where boats can be tied up or secured.
  • C. mooredInState
    Indicates that an object such as a vessel or structure is secured or anchored within the territorial waters or jurisdiction of a specific state.
  • D. mooringType
    Indicates the specific method or system by which a vessel or floating structure is secured in place.
  • E. locatedInHarbourArea
    Indicates that something is situated within the geographic or administrative boundaries of a harbour area.
  • F. None of above.

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_69f348c475348190bf579ca858eec77c completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69fdd2be648c8190b60b3d1caeb44364 completed May 8, 2026, 12:10 p.m.
PD Predicate disambiguation batch_69fdd14a5c708190a6f95ec61f4fc28f completed May 8, 2026, 12:04 p.m.
Created at: April 30, 2026, 9:01 p.m.