Triple
T30312885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bécancour |
E770972
|
entity |
| Predicate | crossedByRoute |
P416
|
FINISHED |
| Object | Route 132 |
—
|
NE NERFINISHED |
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: Route 132 | Statement: [Bécancour, crossedByRoute, Route 132]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossedByRoute Context triple: [Bécancour, crossedByRoute, Route 132]
-
A.
crossedBy
chosen
Indicates that one entity (typically a path, line, or boundary) is intersected or traversed by another entity.
-
B.
crossingOf
Indicates that one entity serves as the intersection or crossing point of two or more linear features, such as roads, paths, or tracks.
-
C.
crossedByHighway
Indicates that a highway passes across or through the extent of a given entity or area.
-
D.
crossedByTunnel
Indicates that one entity (typically a barrier like a mountain, river, or road) is traversed or passed through by another entity via a tunnel.
-
E.
borderCrossingRouteTo
Indicates a route or path used to travel across a border from one place or jurisdiction to another.
- F. None of above.
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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 29, 2026, 7:50 p.m.