Triple
T6338679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sulu Archipelago |
E142562
|
entity |
| Predicate | seaLane |
P10083
|
FINISHED |
| Object | Sulu Sea shipping routes |
—
|
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: Sulu Sea shipping routes | Statement: [Sulu Archipelago, seaLane, Sulu Sea shipping routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seaLane Context triple: [Sulu Archipelago, seaLane, Sulu Sea shipping routes]
-
A.
seaCode
Indicates a standardized code or identifier assigned to a sea or maritime area.
-
B.
seaConnection
Indicates a relationship where two places are connected or accessible to each other via the sea, such as by maritime routes or coastal adjacency.
-
C.
hasMajorSeaLane
chosen
Indicates that a significant maritime shipping or navigation route passes through, borders, or is closely associated with the referenced entity.
-
D.
seaRouteOpened
Indicates that a maritime route between locations has been established and made available for use.
-
E.
associatedWithSeaRoute
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_69c008d4d8e88190ad301c05b08722ac |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0654fb774819087bffb8b966a790a |
completed | March 22, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69c060ea1a988190889e47b7e0c819b8 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:30 p.m.