Triple
T23832025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southwestern Philippines |
E589537
|
entity |
| Predicate | hasMaritimeRoutesTo |
P27556
|
FINISHED |
| Object | Borneo |
—
|
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: Borneo | Statement: [Southwestern Philippines, hasMaritimeRoutesTo, Borneo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaritimeRoutesTo Context triple: [Southwestern Philippines, hasMaritimeRoutesTo, Borneo]
-
A.
hasSeaRouteConnection
chosen
Indicates that there exists a navigable maritime route linking two locations or entities.
-
B.
hasMaritimeConnection
Indicates a relationship in which an entity is linked to seas, oceans, or maritime activities, such as shipping, navigation, or coastal operations.
-
C.
associatedWithSeaRoute
Indicates a relationship where something is connected or related to a particular sea route, such as by use, location, or relevance.
-
D.
hasMajorSeaPort
Indicates that a place possesses at least one significant seaport used for major maritime transport, trade, or shipping activities.
-
E.
hasMajorSeaLane
Indicates that a significant maritime shipping or navigation route passes through, borders, or is closely associated with the referenced entity.
- 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_69e25d1922d481909cab567c06a802ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7f6f25c8190bd8957fe3cbefc03 |
completed | April 29, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 8:05 p.m.