Triple
T10193247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herschel Island |
E238090
|
entity |
| Predicate | hasSeaRoute |
P62174
|
FINISHED |
| Object | near Drake Passage shipping lanes |
—
|
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: near Drake Passage shipping lanes | Statement: [Herschel Island, hasSeaRoute, near Drake Passage shipping lanes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeaRoute Context triple: [Herschel Island, hasSeaRoute, near Drake Passage shipping lanes]
-
A.
hasSeaRouteConnection
Indicates that there exists a navigable maritime route linking two locations or entities.
-
B.
associatedWithSeaRoute
chosen
Indicates a relationship where something is connected or related to a particular sea route, such as by use, location, or relevance.
-
C.
hasSeaVoyage
Indicates that an entity undertakes, includes, or is associated with a journey or travel conducted by sea.
-
D.
hasMaritimeConnection
Indicates a relationship in which an entity is linked to seas, oceans, or maritime activities, such as shipping, navigation, or coastal operations.
-
E.
seaRouteOpened
Indicates that a maritime route between locations has been established and made available for use.
- 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_69ca84de1b208190bf17bb305b002605 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdedc675008190b8248325f5a208bf |
completed | April 2, 2026, 4:17 a.m. |
| PD | Predicate disambiguation | batch_69cd7c8477648190bc55c56aeec507d3 |
completed | April 1, 2026, 8:13 p.m. |
Created at: March 30, 2026, 9:13 p.m.