Triple
T26799785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burleigh Falls |
E671065
|
entity |
| Predicate | hasNearbyLock |
P183703
|
FINISHED |
| Object | Lock 28 Trent–Severn Waterway |
—
|
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: Lock 28 Trent–Severn Waterway | Statement: [Burleigh Falls, hasNearbyLock, Lock 28 Trent–Severn Waterway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyLock Context triple: [Burleigh Falls, hasNearbyLock, Lock 28 Trent–Severn Waterway]
-
A.
hasNearbyAccess
Indicates that one entity has convenient, close-proximity access to another resource, service, or location.
-
B.
hasNearbyMode
Indicates that one entity has another entity located close enough to be considered in its immediate vicinity or surrounding area.
-
C.
hasNearbyGate
Indicates that one entity has a gate located in close physical proximity to it.
-
D.
hasNearbyBay
Indicates that one entity is located close to or adjacent to a bay associated with the other entity.
-
E.
hasNearbyPass
Indicates that an entity has at least one pass (e.g., transit or access pass) available within a short or locally defined distance from it.
- F. None of above. chosen
Provenance (4 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_69eeb31fbd888190a82dac5822e453bc |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f7a283388c81908e4a9ee3369e8d6f |
completed | May 3, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a224365081908ff6958e3b30bd05 |
completed | May 3, 2026, 7:29 p.m. |
Created at: April 27, 2026, 4:22 a.m.