Triple
T448152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Murrumbidgee River |
E7065
|
entity |
| Predicate | hasNavigationUse |
P14917
|
FINISHED |
| Object | limited navigation |
—
|
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: limited navigation | Statement: [Murrumbidgee River, hasNavigationUse, limited navigation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNavigationUse Context triple: [Murrumbidgee River, hasNavigationUse, limited navigation]
-
A.
usedToNavigate
Indicates that one entity served as a means or tool for another entity to find or follow a route or direction.
-
B.
navigatesUsing
Indicates that one entity moves or travels through an environment by relying on another entity as its means, tool, or method of navigation.
-
C.
hasNavigationAid
Indicates that one entity provides or is equipped with a navigation aid used to assist in determining position or direction.
-
D.
enablesNavigationBetween
Indicates that one entity provides the means or capability for moving or transitioning between two other entities or locations.
-
E.
navigatedBy
Indicates that the movement, direction, or operation of something is controlled, guided, or steered by a specified agent.
- 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_69a2e7e4676c81909ea0dbdecac0687c |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef6429e881908aa758da64299a16 |
completed | Feb. 28, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69a2ede1a1108190a4a06b3416ae6156 |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2ef611b9c8190ac5e9174744d9127 |
completed | Feb. 28, 2026, 1:36 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.