Triple
T35994016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sitka fishing fleet |
E1040928
|
entity |
| Predicate | navigatesArea |
P184314
|
FINISHED |
| Object | Inside Passage |
—
|
NE NERFINISHED |
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: Inside Passage | Statement: [Sitka fishing fleet, navigatesArea, Inside Passage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigatesArea Context triple: [Sitka fishing fleet, navigatesArea, Inside Passage]
-
A.
navigationArea
Indicates that a specified region or space is designated for movement, routing, or pathfinding within an environment.
-
B.
hasNavigationArea
Indicates that an entity is associated with or includes a designated area intended for navigation or movement.
-
C.
notableAreaWithin
Indicates that one area is a particularly significant or noteworthy part located inside another, larger area.
-
D.
navigatesUsing
Indicates that one entity moves or travels through an environment by relying on another entity as its means, tool, or method of navigation.
-
E.
navigableTo
Indicates that one entity can be reached or traversed to from another entity, typically following valid paths or connections within a system or environment.
- 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_69f76e29084c819083987b828d414de7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ad15f3b88190b7c9742a734fec5f |
completed | May 3, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69f7acad20388190b9b10270ca9bdfbc |
completed | May 3, 2026, 8:14 p.m. |
Created at: May 3, 2026, 4:07 p.m.