Triple

T6782631
Position Surface form Disambiguated ID Type / Status
Subject Longdendale E155719 entity
Predicate hasTransportIssue P72800 FINISHED
Object traffic congestion on A628 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: traffic congestion on A628 | Statement: [Longdendale, hasTransportIssue, traffic congestion on A628]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTransportIssue
Context triple: [Longdendale, hasTransportIssue, traffic congestion on A628]
  • A. hasTransportRoute
    Indicates that there exists a designated transportation connection or route linking one entity to another.
  • B. carriageIssues
    Indicates that there are problems, malfunctions, or irregularities affecting the operation or condition of a carriage.
  • C. hasGroundTransportation
    Indicates that an entity provides, includes, or is connected to transportation services or options that operate on land (e.g., cars, buses, trains).
  • D. hasTransportationSystem
    Indicates that an entity possesses, operates, or is served by an organized system for transporting people or goods.
  • E. hasTransportationContext
    Indicates that there is a contextual relationship involving transportation modes, conditions, or circumstances relevant to the associated entities or event.
  • F. None of above. chosen

Provenance (4 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_69c688162bf8819088b664b5c3b5be7a completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d289958481908ad4f9467a107083 completed March 27, 2026, 6:55 p.m.
PD Predicate disambiguation batch_69c6d095dcac8190bb9b943f50a7f885 completed March 27, 2026, 6:46 p.m.
PDg Predicate description generation batch_69c6d182213c819086fcbbfd3d64d80b completed March 27, 2026, 6:50 p.m.
Created at: March 27, 2026, 2:14 p.m.