Triple

T19330321
Position Surface form Disambiguated ID Type / Status
Subject Bridge of Earn E483469 entity
Predicate hasNearbyRoad P11435 FINISHED
Object A912 road
The A912 road is a regional route in eastern Scotland that connects several towns in Perth and Kinross and Fife, serving as an important local link between major trunk roads.
E2286939 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: A912 road | Statement: [Bridge of Earn, hasNearbyRoad, A912 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: A912 road
Triple: [Bridge of Earn, hasNearbyRoad, A912 road]
Generated description
The A912 road is a regional route in eastern Scotland that connects several towns in Perth and Kinross and Fife, serving as an important local link between major trunk roads.

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_69d8e8d13e3c81909d91d1d5ec37c095 completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e616412bcc81909bb34d3cf5363129 completed April 20, 2026, 12:04 p.m.
NED1 Entity disambiguation (via context triple) batch_6a47497b998c81908dec1bfa6082f17c completed July 3, 2026, 5:32 a.m.
NEDg Description generation batch_6a474b4a938c819088d90ee6967efaae completed July 3, 2026, 5:40 a.m.
NED2 Entity disambiguation (via description) batch_6a474bdcda2c81908488df6a381cd991 completed July 3, 2026, 5:42 a.m.
Created at: April 10, 2026, 1:33 p.m.