Triple
T32181287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balingoan |
E821987
|
entity |
| Predicate | maritimeRouteImportance |
P108176
|
FINISHED |
| Object | major jump-off point to Camiguin |
—
|
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: major jump-off point to Camiguin | Statement: [Balingoan, maritimeRouteImportance, major jump-off point to Camiguin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maritimeRouteImportance Context triple: [Balingoan, maritimeRouteImportance, major jump-off point to Camiguin]
-
A.
isMaritimeRoute
Indicates that one location is connected to another by a navigable sea or ocean route used for maritime transport.
-
B.
portImportance
chosen
Indicates the relative significance or strategic value of a port within a given context (such as trade, logistics, or transportation networks).
-
C.
marineRouteType
Indicates the specific kind or classification of a maritime route used for travel, transport, or navigation between locations.
-
D.
associatedWithSeaRoute
Indicates a relationship where something is connected or related to a particular sea route, such as by use, location, or relevance.
-
E.
includesTradeRoute
Indicates that one entity contains, encompasses, or makes use of a particular trade route within its scope or structure.
- 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 12:34 a.m.