Triple

T30302323
Position Surface form Disambiguated ID Type / Status
Subject Mount Seymour E770683 entity
Predicate roadAccessFrom P22549 FINISHED
Object Seymour Mainline Road
Seymour Mainline Road is the primary access road leading up to Mount Seymour in British Columbia, Canada, used by visitors to reach the mountain’s recreational areas.
E2293577 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: Seymour Mainline Road | Statement: [Mount Seymour, roadAccessFrom, Seymour Mainline Road]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Seymour Mainline Road
Triple: [Mount Seymour, roadAccessFrom, Seymour Mainline Road]
Generated description
Seymour Mainline Road is the primary access road leading up to Mount Seymour in British Columbia, Canada, used by visitors to reach the mountain’s recreational areas.

Provenance (5 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_69f224881b948190b8c4921b250a44a3 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f6813b03c881909786514932f103f3 completed May 2, 2026, 10:56 p.m.
NED1 Entity disambiguation (via context triple) batch_6a7ac2ff181481909764ac61cadcb4a3 completed Aug. 11, 2026, 6:36 a.m.
NEDg Description generation batch_6a7ac3d0d8e881909489943e43a9f725 completed Aug. 11, 2026, 6:40 a.m.
NED2 Entity disambiguation (via description) batch_6a7ac40451f08190b553a2e4086037d3 completed Aug. 11, 2026, 6:41 a.m.
Created at: April 29, 2026, 7:49 p.m.