Triple
T1165014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newark Bay |
E24579
|
entity |
| Predicate | isNavigable |
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: [Newark Bay, isNavigable, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNavigable Context triple: [Newark Bay, isNavigable, yes]
-
A.
navigableFor
Indicates that one entity (such as a path, route, or medium) can be traversed or used for movement by another entity (such as a vehicle, vessel, or agent).
-
B.
navigableInSection
Indicates that something can be successfully moved through, accessed, or traversed within a specified section or segment.
-
C.
hasNavigationUse
Indicates that something is used for navigation or serves a navigational function in relation to another entity.
-
D.
navigability
chosen
Indicates how easily and effectively something (such as a space, interface, or route) can be traversed or moved through.
-
E.
navigatedBy
Indicates that the movement, direction, or operation of something is controlled, guided, or steered by a specified agent.
- 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_69a494060e148190abb42f971242c197 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bccb3b388190938c68dee90b3f19 |
completed | March 1, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69a4bb548c1481909092626c572d8782 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.