Triple
T27447856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rangsang Island |
E692339
|
entity |
| Predicate | locatedInSeaRoute |
P62174
|
FINISHED |
| Object | Malacca Strait shipping lane |
—
|
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: Malacca Strait shipping lane | Statement: [Rangsang Island, locatedInSeaRoute, Malacca Strait shipping lane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInSeaRoute Context triple: [Rangsang Island, locatedInSeaRoute, Malacca Strait shipping lane]
-
A.
locatedAtSea
Indicates that something exists or is situated in or on the sea.
-
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.
isMaritimeRoute
Indicates that one location is connected to another by a navigable sea or ocean route used for maritime transport.
-
D.
locatedInStrait
Indicates that something is situated within or passes through a narrow body of water (a strait) that connects two larger bodies of water.
-
E.
controlledSeaRoute
Indicates that one entity has authority over, or the ability to regulate and manage access through, a particular maritime route used for navigation or transport.
- 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_69ef5206c9248190b5975c2a7f9d229c |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69fee0b2da3c8190a3519d0564f2f32d |
completed | May 9, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69fee05b315c819081dfcbfb15273487 |
completed | May 9, 2026, 7:20 a.m. |
Created at: April 27, 2026, 12:46 p.m.