Triple
T19283383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paita |
E482244
|
entity |
| Predicate | hasMaritimeConnectionTo |
P27556
|
FINISHED |
| Object | other Pacific ports |
—
|
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: other Pacific ports | Statement: [Paita, hasMaritimeConnectionTo, other Pacific ports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaritimeConnectionTo Context triple: [Paita, hasMaritimeConnectionTo, other Pacific ports]
-
A.
hasMaritimeConnection
Indicates a relationship in which an entity is linked to seas, oceans, or maritime activities, such as shipping, navigation, or coastal operations.
-
B.
hasSeaRouteConnection
chosen
Indicates that there exists a navigable maritime route linking two locations or entities.
-
C.
hasCoastlineOn
Indicates that one entity’s coastline borders or is directly adjacent to a specified body of water.
-
D.
hasLandBorderWithSea
Indicates that an entity’s land area directly borders or touches a sea along its coastline.
-
E.
isSeparatedFromMainlandBy
Indicates that one land area is divided from the mainland by a specific intervening body or feature, such as water or terrain.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbffda78819088bf8dbc61756831 |
completed | April 20, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:30 p.m.