Triple
T4719552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulf of Boothia |
E104729
|
entity |
| Predicate | navigationConditions |
P16300
|
FINISHED |
| Object | difficult |
—
|
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: difficult | Statement: [Gulf of Boothia, navigationConditions, difficult]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationConditions Context triple: [Gulf of Boothia, navigationConditions, difficult]
-
A.
navigationCondition
chosen
Indicates the specific circumstances or requirements that must be satisfied for a navigation action or route to be valid or taken.
-
B.
navigationRegulation
Indicates rules or constraints that govern how navigation or movement is allowed, restricted, or managed within a particular space or system.
-
C.
navigation
Indicates the act or process of determining and following a path or route from one location or state to another.
-
D.
canProvideDirections
Indicates that one entity is able to give another entity guidance or instructions on how to reach a particular location or navigate a route.
-
E.
navigationArea
Indicates that a specified region or space is designated for movement, routing, or pathfinding within an environment.
- 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_69bd43ec4a348190bc41afae43375e71 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd680beb508190b3d74e20e1c64405 |
completed | March 20, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69bd621ddcd88190903288566f5e5dab |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:18 p.m.