Triple
T21985949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canmore |
E542960
|
entity |
| Predicate | hasBrowseFunction |
P146164
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Canmore, hasBrowseFunction, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBrowseFunction Context triple: [Canmore, hasBrowseFunction, true]
-
A.
hasBridgeFunction
Indicates that something serves as an intermediary or connecting function between two otherwise separate components, systems, or entities.
-
B.
hasOnscreenFunction
Indicates that an entity serves a particular role or performs a specific function when it appears on screen.
-
C.
hasFunctionInPresent
Indicates that an entity currently performs, exhibits, or fulfills a specific function or role at the present time.
-
D.
hasNavigationAccess
Indicates that one entity is permitted to access or use the navigation capabilities or navigation-related resources of another entity.
-
E.
hasBridgeAccess
Indicates that an entity is permitted to enter or use a specific bridge or bridge-controlled area.
- 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_69e0c48136b081908831fa907cc02e18 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f12709cb288190a2620e337fea364c |
completed | April 28, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69e6f6154e408190acc5b2c278acaff4 |
completed | April 21, 2026, 3:59 a.m. |
| PDg | Predicate description generation | batch_69e6fad4a540819096cdd5ea08527220 |
completed | April 21, 2026, 4:19 a.m. |
Created at: April 16, 2026, 8:04 p.m.