Triple
T35184708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mona Lake Channel |
E1015952
|
entity |
| Predicate | hasNavigableConnectionBetween |
P94076
|
FINISHED |
| Object | Mona Lake |
—
|
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: Mona Lake | Statement: [Mona Lake Channel, hasNavigableConnectionBetween, Mona Lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNavigableConnectionBetween Context triple: [Mona Lake Channel, hasNavigableConnectionBetween, Mona Lake]
-
A.
navigableFrom
Indicates that one location or entity can be reached or traversed from another, typically via a valid path, route, or connection.
-
B.
isNavigableVia
chosen
Indicates that one entity can be reached, traversed, or accessed by means of another entity (such as a route, medium, or pathway).
-
C.
hasNotableConnectionTo
Indicates a significant or noteworthy relationship, association, or link exists between two entities.
-
D.
hasNavigationalFeature
Indicates that one entity possesses or includes a navigational aid, element, or capability that supports movement, orientation, or route-finding.
-
E.
isNavigableNear
Indicates that an entity can be traversed or passed through in close proximity to another specified entity or location.
- 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_69f76ddd815c8190b822eea06630f9fb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff38b960808190a8263348f1e5c0e4 |
completed | May 9, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69ff37d97d9c8190849b2bac14f9af1d |
completed | May 9, 2026, 1:34 p.m. |
Created at: May 3, 2026, 4:02 p.m.