Triple

T4037540
Position Surface form Disambiguated ID Type / Status
Subject Spitfire Bridge E83861 entity
Predicate hasLocationRelation P17188 FINISHED
Object associated with the route of the M3 motorway in southern England LITERAL 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: associated with the route of the M3 motorway in southern England | Statement: [Spitfire Bridge, hasLocationRelation, associated with the route of the M3 motorway in southern England]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLocationRelation
Context triple: [Spitfire Bridge, hasLocationRelation, associated with the route of the M3 motorway in southern England]
  • A. hasRelativeLocation
    Indicates that one entity is positioned in space in relation to another entity’s location.
  • B. hasLocationComponent
    Indicates that something includes, is associated with, or is composed of a specific location-related part or element.
  • C. spatialRelation chosen
    Indicates a spatial relationship between entities, specifying how one is positioned or located relative to another in space.
  • D. hasRelation
    Indicates that there exists some specified relationship or association between two entities.
  • E. refersToLocation
    Indicates that one entity designates, points to, or identifies a specific location associated with it.
  • 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_69aed92f7cf0819098e0539bdcc3767f completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefb3656f08190aa5286d951013646 completed March 9, 2026, 4:54 p.m.
PD Predicate disambiguation batch_69aef900386481909d04555a9ec9b0e3 completed March 9, 2026, 4:44 p.m.
Created at: March 9, 2026, 3:36 p.m.