Triple
T17360083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dumai |
E422044
|
entity |
| Predicate | hasNearbySeaRoute |
P62174
|
FINISHED |
| Object | international shipping lane in Strait of Malacca |
—
|
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: international shipping lane in Strait of Malacca | Statement: [Dumai, hasNearbySeaRoute, international shipping lane in Strait of Malacca]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbySeaRoute Context triple: [Dumai, hasNearbySeaRoute, international shipping lane in Strait of Malacca]
-
A.
hasSeaRouteConnection
Indicates that there exists a navigable maritime route linking two locations or entities.
-
B.
hasDestinationSea
Indicates that something is directed or travels toward a sea as its endpoint or target location.
-
C.
hasNearbyHarbor
Indicates that one location has a harbor situated close to it in geographic proximity.
-
D.
hasNearbyCoast
Indicates that one location is situated close to a coastline or seashore.
-
E.
associatedWithSeaRoute
chosen
Indicates a relationship where something is connected or related to a particular sea route, such as by use, location, or relevance.
- 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a4cacd881909fd722068b019f25 |
completed | April 19, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.