Triple
T485664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neva River |
E9869
|
entity |
| Predicate | navigable |
P13009
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Neva River, navigable, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigable Context triple: [Neva River, navigable, yes]
-
A.
navigability
chosen
Indicates how easily and effectively something (such as a space, interface, or route) can be traversed or moved through.
-
B.
navigation
Indicates the act or process of determining and following a path or route from one location or state to another.
-
C.
navigatedBy
Indicates that the movement, direction, or operation of something is controlled, guided, or steered by a specified agent.
-
D.
usedToNavigate
Indicates that one entity served as a means or tool for another entity to find or follow a route or direction.
-
E.
navigatesUsing
Indicates that one entity moves or travels through an environment by relying on another entity as its means, tool, or method of navigation.
- 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_69a2e802e2908190ab17c9479e0b6412 |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f0bb46788190b40182bf2a54f98f |
completed | Feb. 28, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69a2edf48ec08190b85d07e194f99c49 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.