Triple
T37271994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamilton Inlet |
E924537
|
entity |
| Predicate | hasNavigationRouteTo |
P53909
|
FINISHED |
| Object | Happy Valley-Goose Bay |
—
|
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: Happy Valley-Goose Bay | Statement: [Hamilton Inlet, hasNavigationRouteTo, Happy Valley-Goose Bay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNavigationRouteTo Context triple: [Hamilton Inlet, hasNavigationRouteTo, Happy Valley-Goose Bay]
-
A.
hasNavigationRoute
chosen
Indicates that one entity provides or defines a navigation path or route leading to or through another entity.
-
B.
hasRoute
Indicates that there exists a path or connection enabling travel or communication from one entity to another.
-
C.
hasNavigationPass
Indicates that an entity possesses a valid authorization or pass granting it navigation or passage rights within a specified area or route.
-
D.
hasNavigationStatus
Indicates the current state or condition of an entity’s navigation, such as whether and how it is actively navigating.
-
E.
hasNavigationUse
Indicates that something is used for navigation or serves a navigational function in relation to another entity.
- 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_69f76eacdd8c819094080d3991e6d37c |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff965f9be48190b015b788207be676 |
completed | May 9, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69ff95d3015c8190b9d293fe31b859c3 |
completed | May 9, 2026, 8:15 p.m. |
Created at: May 3, 2026, 4:15 p.m.