Triple
T7528262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papeete |
E177950
|
entity |
| Predicate | isConnectedBySeaRoutesTo |
P27556
|
FINISHED |
| Object | other Society Islands |
—
|
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 Society Islands | Statement: [Papeete, isConnectedBySeaRoutesTo, other Society Islands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isConnectedBySeaRoutesTo Context triple: [Papeete, isConnectedBySeaRoutesTo, other Society Islands]
-
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.
neighboringCountryBySea
Indicates that one country is adjacent to another with their territories touching via a shared sea boundary rather than solely by land.
-
D.
isSeparatedFromMainlandBy
Indicates that one land area is divided from the mainland by a specific intervening body or feature, such as water or terrain.
-
E.
hasCoastlineOn
Indicates that one entity’s coastline borders or is directly adjacent to a specified body of water.
- 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_69c69f29bf3081909a146aec7755f185 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f81e19208190965f211d057f7fdf |
completed | March 27, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d6bb808190bdd04499fd3bceb6 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:47 p.m.