Triple
T7355825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carrying Place, Ontario |
E169621
|
entity |
| Predicate | hasPortageRoute |
P4374
|
FINISHED |
| Object | between Bay of Quinte and Lake Ontario |
—
|
LITERAL 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: between Bay of Quinte and Lake Ontario | Statement: [Carrying Place, Ontario, hasPortageRoute, between Bay of Quinte and Lake Ontario]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPortageRoute Context triple: [Carrying Place, Ontario, hasPortageRoute, between Bay of Quinte and Lake Ontario]
-
A.
hasPortOn
Indicates that one entity possesses or is located adjacent to a port situated on another specified geographic or infrastructural feature (such as a coast, river, or lake).
-
B.
hasPortico
Indicates that one entity (typically a building or structure) features a portico as part of its architectural design.
-
C.
hasRoute
chosen
Indicates that there exists a path or connection enabling travel or communication from one entity to another.
-
D.
hasPortal
Indicates that one entity possesses or provides access to a portal connecting to another location or entity.
-
E.
hasPortCode
Indicates that an entity (such as a port or terminal) is associated with a specific standardized port code identifier.
- 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_69c68a59f2288190877ca15c19b1e822 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f26d6d6081909c7272a9ccae0d97 |
completed | March 27, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69c6f02d36108190bcb34a95e6a30bd7 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:05 p.m.