Triple
T1067671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Pérouse Strait |
E23248
|
entity |
| Predicate | isPartOfSeaRoute |
P6309
|
FINISHED |
| Object | routes between East Asia and North Pacific |
—
|
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: routes between East Asia and North Pacific | Statement: [La Pérouse Strait, isPartOfSeaRoute, routes between East Asia and North Pacific]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfSeaRoute Context triple: [La Pérouse Strait, isPartOfSeaRoute, routes between East Asia and North Pacific]
-
A.
isPartOfRoute
chosen
Indicates that something (such as a segment, stop, or step) belongs to and is contained within a larger route.
-
B.
seaRouteOpened
Indicates that a maritime route between locations has been established and made available for use.
-
C.
isPortOfCallFor
Indicates that a location serves as a scheduled stop or destination for a ship, vehicle, or journey.
-
D.
hasMajorSeaLane
Indicates that a significant maritime shipping or navigation route passes through, borders, or is closely associated with the referenced entity.
-
E.
hasFerryPort
Indicates that a place serves as a location where ferries regularly dock to load and unload passengers or cargo.
- 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_69a493ee1f908190992b5f0d1b04459b |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b9e1047481909af1cf8df2a01fff |
completed | March 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69a4b736f1e881909bace735b38c0ade |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.