Triple
T30698016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caledonia, Ontario |
E781528
|
entity |
| Predicate | bridge |
P2535
|
FINISHED |
| Object |
Caledonia Bridge
Caledonia Bridge is a historic multi-span road bridge over the Grand River in Caledonia, Ontario, known as a prominent local landmark and key transportation crossing.
|
E2088854
|
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: Caledonia Bridge | Statement: [Caledonia, Ontario, bridge, Caledonia Bridge]
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: Caledonia Bridge Triple: [Caledonia, Ontario, bridge, Caledonia Bridge]
Generated description
Caledonia Bridge is a historic multi-span road bridge over the Grand River in Caledonia, Ontario, known as a prominent local landmark and key transportation crossing.
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_69f224ab24e08190991d6edb6df58e8b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68bdceb8c8190b78e499ea2357e0f |
completed | May 2, 2026, 11:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36e5fbcdb0819099c20a337a9c0f99 |
completed | June 20, 2026, 7:11 p.m. |
| NEDg | Description generation | batch_6a36e90d94788190b528a81f3cafe3b3 |
completed | June 20, 2026, 7:25 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a36e9736fc48190990a081dc29457f5 |
completed | June 20, 2026, 7:26 p.m. |
Created at: April 29, 2026, 8:34 p.m.