Triple

T5120699
Position Surface form Disambiguated ID Type / Status
Subject Perimeter Highway E115454 entity
Predicate connectsTo P845 FINISHED
Object PTH 101 E495622 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: PTH 101 | Statement: [Perimeter Highway, connectsTo, PTH 101]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: PTH 101
Context triple: [Perimeter Highway, connectsTo, PTH 101]
  • A. PTH 101 chosen
    PTH 101 is a provincial highway in Manitoba, Canada, forming part of the ring road system around the city of Winnipeg.
  • B. PTH 1
    PTH 1 is a major provincial highway in Manitoba, Canada, forming part of the Trans-Canada Highway and serving as a primary east–west transportation route across the province.
  • C. PTH 100
    PTH 100 is a major ring road route forming part of the Perimeter Highway system around Winnipeg, Manitoba.
  • D. PTH 15
    PTH 15 is a provincial highway in Manitoba, Canada, serving as an important east–west route linking Winnipeg to communities to the east.
  • E. PTH 2
    PTH 2 is a provincial highway in Manitoba, Canada, that serves as a key east–west transportation route southwest of Winnipeg.
  • 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_69bd4442ade0819087b9461f892b206b completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd78015ad88190a3e51da494c19e30 completed March 20, 2026, 4:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69bed9185b9481908afd32bdeefa3f1e completed March 21, 2026, 5:44 p.m.
Created at: March 20, 2026, 1:42 p.m.