Triple
T11506903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canal de Savières |
E272807
|
entity |
| Predicate | hasNavigationalStatus |
P43423
|
FINISHED |
| Object | navigable |
—
|
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: navigable | Statement: [Canal de Savières, hasNavigationalStatus, navigable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNavigationalStatus Context triple: [Canal de Savières, hasNavigationalStatus, navigable]
-
A.
hasNavigationStatus
Indicates the current state or condition of an entity’s navigation, such as whether and how it is actively navigating.
-
B.
navigationStatus
chosen
Indicates the current state or condition of an entity’s navigation process, such as whether it is actively navigating, idle, or has encountered an issue.
-
C.
hasNavigationControl
Indicates that one entity possesses authority or capability to direct, manage, or influence the movement or course of another entity.
-
D.
hasNavigationCharacteristic
Indicates that an entity possesses a specific property, feature, or quality related to navigation or navigational behavior.
-
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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d86db43a648190be859bec2fe9f43b |
completed | April 10, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69d80876e5f0819088cff2e72f773cf6 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.